Hi, I've never used Jinga, so I can't answer those questions.
Concerning your first question, one way you can keep the cache fresh is to update or delete the cache if an entity is changed, in addition to setting a default expiration time. As for the third question, there is no way to automatically 'expire' an entity. You would need to periodically run a handler that would update/delete old entities to accomplish this. -Marzia On Tue, Dec 2, 2008 at 9:44 AM, gops <[EMAIL PROTECTED]> wrote: > > In my app , i use one query to retrive 10 results. > > e.g. > > A = B.all().fetch(10) > > cached it via memcache and served it. > > now my question is , if any one of that 10 entity changed , How do I > know -- to not to serve memcache and query the database again. > > --- > anybody using jinja ?? -- I would like to know , how to implement > "slugify" like tag/filter ?? > > and does caching template via memcache helps speeding up things? -- > making memcache loader is quite easy , but will it help ? > and how do one cache compiled bytecode in jinja in to memcache ? > > or is there any app engine specific version of jinja is available ? > --- > another question is , how can i make my entity die after particular > time <-- it can be > done manually .. but is there any automatic/built in way ? > > -- > sorry for asking too many question. :D but i need help...... > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
