Why not use a chained cache.disk inside a cache.ram. This way it caches to both, so if it doesn't have cached in ram, it can always pull from the disk.
I'm curious, what is the object your trying to cache ? I would think any object that had to persist in a thread-safe way like your requirements should be redesigned and stored in a database. -Thadeus On Sun, Jan 31, 2010 at 8:09 PM, Mark Larsen <[email protected]> wrote: >> FWIW, I had good results in a previous project using a recipe from >> Massimo for a ram cached threadsafe class. I wasn't using Apache, >> though. > > Mike, that looks really promising. I imagine I could come up with a > way to get all the apache processes to cache the same object after the > server starts. If I remember correctly about the mod_wsgi and apache, > I'd have a duplicate object for each process but since I'm only > interested in reading from it with very infrequent updates to it (and > ram is cheap), it wouldn't be a big deal. > > -- > You received this message because you are subscribed to the Google Groups > "web2py-users" 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/web2py?hl=en. > > -- You received this message because you are subscribed to the Google Groups "web2py-users" 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/web2py?hl=en.
