Who is to say this isn't by design? Updating all your caches on demand isn't always needed. Sometimes you let things delay a bit, for the sake of reducing load.
On Sat, Dec 6, 2008 at 1:22 PM, edwin <[EMAIL PROTECTED]> wrote: > > Hi, > > [Not sure if this the appropriate place to report this kind of problem > (please tell me if so)] > > I've noticed a small error on this example: > http://code.google.com/appengine/docs/memcache/usingmemcache.html > > It caches the greetings, but never clears them, and as such after > adding a new greeting, it will only show up when the cache expires. > This is very noticable when using the development webserver. > > The solution is easy, just add a memcache.delete("greetings") in > Guestbook::post, before self.redirect. > > P.S.: all the documentation talks about megacycles quota, but > dashboard shows Gigabyte > > > > -- Read my blog! I depend on your acceptance of my opinion! I am interesting! http://techblog.ironfroggy.com/ Follow me if you're into that sort of thing: http://www.twitter.com/ironfroggy --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
