On Tue, Feb 09, 2010 at 03:15:05AM -0800, P?teris Caune wrote: > One thing to keep in mind is that if you'll deploy your webapp with > Apache and mod_wsgi, there will be multiple processes running you app, > and each one will have g object with its own cache. So a bit of memory > wasted and possible data integrity issues: request A gets served by > process A and updates/invalidates A cache , request B gets served by > process B, assumes up-to-date cache but gets stale data. So in that > setting cache should be stored somewhere external where it can be > shared among processes. Like memcached or files.
Ah crap - I didn't even think of that. That's what I get for developing on an environment that's different than production! Guess I'm stuck putting together a standalone server process to handle this. -- Ross Vandegrift [email protected] "If the fight gets hot, the songs get hotter. If the going gets tough, the songs get tougher." --Woody Guthrie
signature.asc
Description: Digital signature
