What about the memcache? Data stored in memcache can be accessed by different instances of your webapp. If you don't specify an expiry time, they'll persist forever, until there's significant load on the cache.
http://code.google.com/appengine/docs/memcache/ On Wed, 31 Dec 2008 09:36:26 +1100, slmnhq <salman....@gmail.com> wrote: > > Hi, > > Some applications have system variables like 'DEBUG_ENABLE', > 'MAP_API_KEY', etc that can change the overall behavior of the > application. > > What is the best way to represent this data in our application? > > One way to do this is have a module that exports this information as > variables. This works fine if we never need to change this data at > runtime. But what if an admin needs to change a system variable? > > Is the answer here to use the datastore? How have other people done > this? > > Thanks, > Salman > > -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---