Gregory (Grisha) Trubetskoy
grisha at modpython.org
Tue May 29 08:35:11 EST 2001
This does indeed seem to be a FAQ, but I don't know if there is a straight answer to it. In *my* opinion, trying to maintain state within the server is not scalable and should be avoided. State should be maintained on the client side with cookies and url's. Since Apache 1.3 runs multiple processes, it is impossible to share memory between them and therefore maintain state in the server. But even with the new Apache 2.0 (which mod_python does not yet support), which will be multithreaded, I would stay away from putting state on the server. If I ever decided that my site is too busy and needs balancing across multiple servers, I'd be in trouble... Also consider situations when a request may never reach a server because of some cache inbewteen. Grisha On Tue, 29 May 2001, Bo Lorentsen wrote: > Hi ... > > I have been trying to write a entry in the mod_python FAQ, but I'm a > quite inpatient person, so I'll ask here too :-) > > I really like the way this mod_python thing works, but I have > desperately trying to find a way to store session based data, but > without luck. > > Is there a way, or is it necessary to store the session data in a > separate data array, that is mapped to some kind of user Apache info ? > This could be a dumb question, as my knowledge about Apache is quite > limited, so I hope you will forgive if this should be quite obvious. > > > /BL > > _______________________________________________ > Mod_python mailing list > Mod_python at modpython.org > http://www.modpython.org/mailman/listinfo/mod_python >
|