I would suggest having a look at the example code in http://backends-io.appspot.com/static/counter_demo.zip.
The code gives examples of how to use urlfetch to communicate between a fronend and a backend. The backend (counter.py) also keeps the value in memory, and writes out changes either within two seconds of modifying the data, or when a shutdown notification occurs (which ever happens first). On 12 May 2011 08:23, Vanni Totaro <[email protected]> wrote: > Hi Richard. > Memcache by design will do eviction. You should keep your backend instance > data in memory (e.g. global var). Be aware that even backend instance could > be killed by the engine, so periodically store live status data in db. > Hope it helps. > Vanni > > -- > 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. > -- 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.
