Thanks. I was hoping I can stick a dictionary somewhere in web.py process. It sounds like a useful thing to do but it's only useful when there is only one web.py process running. But given my simple set up, I'm trying to avoid running an external server like memcached. Maybe a singleton object that does some persistence and locking is what I need.
On Fri, Oct 30, 2009 at 12:46 AM, Frank Smit <[email protected]> wrote: > > Maybe you can use Redis or Memcached. > > 2009/10/30 jlist9 <[email protected]>: >> >> Forgot to mention, I mean in memory, not in database. >> The data will be persisted on disk as well but I prefer not to >> read from disk every time. Instead, I'm thinking the requests >> should read from memory. When there is an update, update >> both in memory and on disk. >> >> On Fri, Oct 30, 2009 at 12:11 AM, <[email protected]> wrote: >> >>> In my app, a request needs to update some data that's shared >>> by the other requests. I wonder if there is a mechanism in web.py >>> to store and access shared data like this? >>> >>> Thanks >> >> > >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web.py" 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/webpy?hl=en -~----------~----~----~----~------~----~------~--~---
