hi Massimo, thanks for the feedback. i was contemplating cache.ram but as you mentioned, once the app moves into production and is front ended by Apache, this solution will not work. it seems that i have to either serialize the data (which means turning off thread.lock with the objects that i'm dealing with), or i need to rethink the logic in this portion of the application.today definitely feels like a Monday! :)
cheers! On Jul 3, 12:47 am, mdipierro <[email protected]> wrote: > This technically not possible because there may not a persistent > process on the server between two http requests in the same session. > It is normal in fact in a production environment to have multiple > processes, each multiple threads. The web severs turns them on and off > freely. The only way the concept of session can be implemented is by > using session variables that are serialized or by using caching (in > general caching is also serialized except for cache.ram). > > You can try use cache.ram but it is a bit tricky because you would > store more and more data in the cache.ram as more sessions are > created. How would you determine when a session has ended and cache > can be cleared? If you do not do this you have a memory leak. > > Anyway this would not work reliably in a production environment with > apache (cache.ram works but only at the level of the process, not at > the level of the session). > > On 2 Lug, 10:04, Jacques van der Merwe <[email protected]> wrote: > > > greetings all, > > > i have a question regarding storing data between controllers. i > > located similar posts regarding this, where the solution was to use > > the Session object to store data. the problem i'm experiencing however > > is that i need to store multiple objects, that are thread locked. this > > a problem using the Session as storage because cPickle throws an > > exception as you cannot serialize an object that is in thread.lock > > state which mine are. my objects do not need to be serialized and are > > only required for the length of the user's session. > > > i was thinking of adding an additional class to globals.py which has > > similar attributes to Session, but does not serialize its contents. > > > i'm still learning the framework so apologies in advance for any > > newbie-ish questions. :) > > > cheers!
