Thanks. I will use CachingDatastoreService - As a suggestion, you should put a list of customers using it so that they know that it's proven.
On Apr 18, 12:22 pm, Jeff Schnitzer <j...@infohazard.org> wrote: > On Wed, Apr 18, 2012 at 2:45 PM, cloudpre <pbx.ku...@gmail.com> wrote: > > Thanks Robert. > > > Jeff - thanks for chipping in. > > > I wanted to check if puts are also cached - eg: entity with same > > values being written over and over again - will they be actually be > > written to datastore. > > The cache is write-through; all put()s go straight to the datastore > and then expire the cache content. The cache is refreshed on a > subsequent get(). > > > I will use 3.1 - I liked the Global cache very much. > > > Twig kept the syntax simpler but I do not like the lack of caching > > which will affect the high-volume apps. > > If you're just using the low-level api, the CachingDatstoreService in > the Objectify 3.1 jar is the same as what's in trunk (Objectify4). If > you're actually thinking of using Objectify, grab trunk - Objectify4 > has a more Twig-ish syntax and has folded in many of Twig's features > (with John Patterson's design help). > > Jeff -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
