The biggest void in the AJAX discussion, IMO, is how network and server availability affects XMLHttpRequests. I can only guess this void is a result of skill set - if you’re hot with CSS is issues relating to UI design, chances are you’re less fluent in the fine print of HTTP or used to thinking in terms of writing fault tolerant clients to remote services.
That gets further compounded by developing on localhost where you don’t get to see the impact of synchronous requests, for example, when the network or remote server is taking a break.
Issues with ASYNC requests in Live Environments
Getting back on track, there’s probably two major issues that occur to me with ASYNC requests, which aren’t solved “by default” by the XMLHttpRequest object.
Dealing with Delay: if the network or remote server is taking it’s time, how does that relate to your AJAX application?
Response Sequencing: network (or server) latency may vary over time. That means responses may not return in the order they were requested.
 Read more...
|
Rate this Ajax Articles
Error connecting to mysql
|
|
Special offer for AjaxImpact.com Visitors!!
Subscribe to Oracle Magazine for Free!
