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.


Reply via email to