Hello Pertti, When people talk about client-side caching, they usually mean using the HTML5 LocalStorage API (accessible via Javascript on the client-side computer).
Here's a good technical overview from Mozilla, including sample code: https://developer.mozilla.org/en-US/docs/Web/Guide/DOM/Storage . If your site uses jQuery, you're in luck because jQuery makes it very easy to access localstorage: http://www.jquerysdk.com/api/jQuery.localStorage . And just for completeness sake, here's an overview of localstorage from Google (this is a Google Web Toolkit page, but much of the basics are still applicable) https://developers.google.com/web-toolkit/doc/latest/DevGuideHtml5Storage . ----------------- -Vinny P Technology & Media Advisor Chicago, IL My Go side project: http://invalidmail.com/ On Friday, June 14, 2013 1:40:55 AM UTC-5, Pertti Kellomäki wrote: > > I am implementing client side caching for editable but mostly unchanging > data. My plan is to split entities in two in the way described in the > Google I/O talk "Building scalable complex apps". The child part contains a > timestamp and a few properties needed for queries, and the parent part > contains the rest of the data. > > There's a lot of stuff out there on client side caching, and a fair bit on > caching inside app engine, but I did not find anything specifically on > client side caching with app engine. Any pointers or insights would be > welcome. > -- > Pertti > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
