Comments on: An AJAX Caching Strategy http://ajaxian.com/archives/an-ajax-caching-strategy Cleaning up the web with Ajax Thu, 17 May 2012 07:43:39 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Allen http://ajaxian.com/archives/an-ajax-caching-strategy/comment-page-1#comment-8858 Allen Fri, 05 May 2006 17:32:44 +0000 http://ajaxian.com/archives/an-ajax-caching-strategy#comment-8858 @James At first glance your 100% correct, and when it comes down to it, standard practices in ajax caching (i.e. its nonexistant heh) will do the trick. But when your dealing with sending / receiving large amounts of data, triggering queries each time, etc, and on a large scale, you can run into problems. Max connections can be an issue in itself (yeah i know, its a stretch). There is no end all cache solution for Ajax, so my writeup will cover as many specialty niche's / cases as possible. Also, there are implications on the client side as well, if a user has already looked up data with an xhr call, why should they ever have to look it up again? It *should* be cached if it can be. @James
At first glance your 100% correct, and when it comes down to it, standard practices in ajax caching (i.e. its nonexistant heh) will do the trick. But when your dealing with sending / receiving large amounts of data, triggering queries each time, etc, and on a large scale, you can run into problems. Max connections can be an issue in itself (yeah i know, its a stretch). There is no end all cache solution for Ajax, so my writeup will cover as many specialty niche’s / cases as possible.

Also, there are implications on the client side as well, if a user has already looked up data with an xhr call, why should they ever have to look it up again? It *should* be cached if it can be.

]]> By: Brandon http://ajaxian.com/archives/an-ajax-caching-strategy/comment-page-1#comment-8856 Brandon Fri, 05 May 2006 16:58:40 +0000 http://ajaxian.com/archives/an-ajax-caching-strategy#comment-8856 I'm interested in this and would like to see your article, Allen. I’m interested in this and would like to see your article, Allen.

]]> By: James MacFarlane http://ajaxian.com/archives/an-ajax-caching-strategy/comment-page-1#comment-8844 James MacFarlane Fri, 05 May 2006 13:47:55 +0000 http://ajaxian.com/archives/an-ajax-caching-strategy#comment-8844 "Making HTTP requests willy-nilly from AJAX applications, however, is almost never a good idea or design decision. The server side of the equation may not be able to handle the flood of requests." Baloney! What's the difference between an Ajax application requesting a little squirt of data, and a browser requesting an ENTIRE PAGE? If a user is going to click on something they're making a request from the server regardless. Users do that "willy nilly" too A smaller data packet means the server will complete the request SOONER and be available for more requests. “Making HTTP requests willy-nilly from AJAX applications, however, is almost never a good idea or design decision. The server side of the equation may not be able to handle the flood of requests.”

Baloney! What’s the difference between an Ajax application requesting a little squirt of data, and a browser requesting an ENTIRE PAGE? If a user is going to click on something they’re making a request from the server regardless. Users do that “willy nilly” too

A smaller data packet means the server will complete the request SOONER and be available for more requests.

]]> By: Allen http://ajaxian.com/archives/an-ajax-caching-strategy/comment-page-1#comment-8839 Allen Fri, 05 May 2006 13:06:48 +0000 http://ajaxian.com/archives/an-ajax-caching-strategy#comment-8839 theres so many different instances and cases where you would need to cache in ajax, and this isnt one (it should be done at the server / proxy level in this case). I'll start working on a big caching article tonight. theres so many different instances and cases where you would need to cache in ajax, and this isnt one (it should be done at the server / proxy level in this case). I’ll start working on a big caching article tonight.

]]>