On Mon, Sep 29, 2008 at 1:16 AM, boonez <[EMAIL PROTECTED]>wrote: > > Hi Everyone, > > There is a caching issue with satchmo. After reviewing the code I see > there are "global" variables in the satchmo caching. This works great > when running directly from the python interpreter however when running > under apache since it is multi threaded the cache will only work when > hit by the same process. > > Just a heads up. > > The satchmo caching is very elequently written though. Easy to read > the code and follow....
Argh, you are partially right. I am using a global for calls and key tracking. However, it does not stop the caching system from working even in a multi-threaded situation, since even if the key isn't tracked in the global key cache, the system will still request it from the cache with cache_get, and delete it with cache_delete or set it with cache_set. The problem is that the cache status admin page may not work properly in that situation. That page allows you to spec. a key and its children to be removed. That won't work reliably in a multi-threaded situation. Nor will the stats be accurate, the cache calls will be far higher than reported, since it will only be reporting calls from one of the threads. However, having just reviewed the code, I can say with assurance that if you are using the memcached backed, then the admin page *will* work for deleting all keys, and regardless of your backend, the cache set/delete/get functions will all work properly and as advertised. Bruce Kroeze http://gosatchmo.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Satchmo 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/satchmo-users?hl=en -~----------~----~----~----~------~----~------~--~---
