Tuesday, May 30th, 2006
Asynchronous or remote scripting has been lurking in the background of web app development for quite some time now. Originally dependent on proprietary technology like Java applets, ActiveX and Flash or clever combinations of disparate technologies like images and cookies, native support for the XMLHttpRequest (XHR) object in modern browsers has made it easier than ever to make web apps more responsive and more like their desktop counterparts. This lower barrier to entry also makes it easier to make poor decisions and inappropriate use of a powerful technology.
So whatâ€™s a well-intentioned web developer to do? Stop and think about the following before dropping that sudsy, lemon-scented bomb on unsuspecting users.
He suggests a few points developers should ponder before even taking the first step to adding Ajax functionality to their applications. This includes using the right tool for the right job (is it content you’re pulling or an action you’re doing?) and how to inform users that the applications is still doing something even when it can’t be seen. Be sure to check out the comments on this one as well – several great points are made.
Posted by Chris Cornutt at 2:39 pm