On Friday, June 14, 2013 12:32:29 PM UTC-5, Pertti Kellomäki wrote:
> Hi Vinny,
>
> Thanks for the pointers. My app uses Angular and some jQuery so
> LocalStorage should be a breeze I guess. What I am really looking for is
> some insight into how to minimize the app engine related cost of keeping
> the client side cache (relatively) up to date.
>
> The design I have so far is to have a separate ModTime class, which has a
> single DateTimeProperty with auto_now=True. ModTimes are attached to
> entities with the parent relation so that I can construct a ModTime key
> from the entity key as ndb.Key('ModTime', 'modtime', parent=entity_key).
> The client can then easily ask whether the locally cached value is up to
> date. Datastore cost is minimized as only the ModTime entity needs to be
> read.
>
>
There's nothing wrong with the scheme you just sketched out. The only thing
I would add is that on the AppEngine side to cache your entities in
Memcache, so you can try there before you go querying to the datastore. Of
course, you probably knew that already, right?
:-) https://groups.google.com/d/msg/google-appengine/aLz-fwheQH8/L_3gFQm6J7EJ
-----------------
-Vinny P
Technology & Media Advisor
Chicago, IL
My Go side project: http://invalidmail.com/
--
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.
