On Wed, 16 Feb 2000, Evan Simpson wrote:
----- Original Message ----- From: Hung Jung Lu <hungjunglu@hotmail.com>
I am thinking in implementing RAM session management. The picture I have is:
(1) Implementing a mini TCP/IP server at a port in an internal server machine. Most likely I'll use Python.
(2) The web server then talks to the session server via TCP/IP.
Does this scheme seem OK? (Security, performance, scalabilty, etc.)
You could also consider metakit, which is now open source. It would be nice to wrap it in Zope and I believe has an option of creating views in memory with no associate disk storage. I *really* want to find some time to wrap metakit in Zope but it won't happen for a while. Alternatively you can save the data in a dict object attached to some persistent object. If you access that dict object through its methods then nothing is going to be registered with the transaction manager, but as that object is going to be referenced frequently then it will stay in memory. This is essentially how FSSession works, but the in memory part lasts only for the period of a transaction. Pavlos