http://learningremix.net/w2007integ/vangoori/ en-us Copyright 2007 Thu, 01 Feb 2007 16:41:58 -0500 http://www.sixapart.com/movabletype/ http://blogs.law.harvard.edu/tech/rss http://www.devx.com/webdev/Article/28861]]> http://learningremix.net/w2007integ/vangoori/2007/02/using_the_xmlhttprequest_object_and_ajax_to_spy_on_you_1.shtml http://learningremix.net/w2007integ/vangoori/2007/02/using_the_xmlhttprequest_object_and_ajax_to_spy_on_you_1.shtml Ajax IS696 Xml Thu, 01 Feb 2007 16:41:58 -0500 http://developers.sun.com/ajax/web2_0_preso.pdf]]> http://learningremix.net/w2007integ/vangoori/2007/01/about_web_20.shtml http://learningremix.net/w2007integ/vangoori/2007/01/about_web_20.shtml IS696 Web2.0 Sun, 28 Jan 2007 19:10:32 -0500 http://java.sun.com/developer/technicalArticles/J2EE/AJAX/]]> http://learningremix.net/w2007integ/vangoori/2007/01/about_ajax.shtml http://learningremix.net/w2007integ/vangoori/2007/01/about_ajax.shtml Ajax IS696 Sun, 28 Jan 2007 16:35:07 -0500 Any developer considering its adoption should be aware of the downsides, such as: * Limited Capabilities: Some Ajax applications are certainly doing things people never dreamed were possible on the web, but there are still substantial restrictions of the web platform. For example: multimedia capabilities, local data storage, real-time graphics, interaction with hardware such as printers and webcams. Support for some of these are improving in recent browsers, some can be achieved by delegating to Flash, but many are simply not possible, and if required, would rule out Ajax. * Performance Concerns: Constant interaction between browser and server can make an application feel unresponsive. There are, however, quite a few well-known patterns for performance optimization such as browser-side caching. These usually suffice, even for fast-paced applications like stock trading, but Ajax still might not work for really time-critical applications such as machine control. * Internet Access Required: The user can't access an Ajax application in the absence of a network connection. * Second Programming Language: Serious Ajax applications require some knowledge of Javascript. Many developers are discovering that Javascript is actually a more capable language than at first assumed, but there is nevertheless an imposition to use a language different to that on the server-side. * Easily Abused: As with any powerful technology, Ajax concepts can be abused by careless programmers. The patterns on this site are intended to guide developers towards more usable solutions, but the fact remains that Ajax isn't always used in a manner that supports usability. www.ajaxpatterns.org http://learningremix.net/w2007integ/vangoori/2007/01/the_downsides_of_ajax.shtml http://learningremix.net/w2007integ/vangoori/2007/01/the_downsides_of_ajax.shtml Ajax Sun, 28 Jan 2007 16:30:16 -0500 Web applications can be a challenging endeavor where you try to get your customers to wait for data to load or pages to render. But with Ajax (sometimes called Asynchronous JavaScript and XML) you can create multi-purpose Web applications that feel like desktop applications. No more waiting for pages to load, and the hourglass is gone. Ajax allows you to create interactive Web applications using: XHTML, CSS, the DOM and JavaScript, and XMLHttpRequest. It is sometimes called Asynchronous JavaScript and XML. You can use Ajax to create more dynamic and interactive Web pages without needing to refresh or reload the page. It only works on the more advanced browsers (6.x) http://learningremix.net/w2007integ/vangoori/2007/01/what_is_ajax_and_what_does_it_allow_you_to_do.shtml http://learningremix.net/w2007integ/vangoori/2007/01/what_is_ajax_and_what_does_it_allow_you_to_do.shtml Ajax IS696 Sun, 28 Jan 2007 16:13:29 -0500