Aaron Held [mailto:[EMAIL PROTECTED]] wrote:
> > If someone wants to propose a NonPersistentMemory store as an 
> > experimental feature, I could see including it.  But I want 
> > to release 
> > 0.8b2 on Wednesday, and I would like ot to be a final beta 
> prior to release.
> 
> What is meant by NonPersistentMemory?
> Are we talking about when the app server shutsdown and restarts?
> I had a problem where when I restarted the app server I did not want
> the old sessions, so I added like to clean the seesion folder.

NonPersistentMemory would be like the Memory store except that it would
never pickle the sessions to disk or load sessions from disk.  When you stop
the appserver you'd lose all sessions.

> I think that the next session code / API upgrade should pay more 
> attention to the load balacing and app server affinity. - Maybe a 
> session prefix code could tell the adapter what server the session 
> started on - so the adapter could keep that user on that app 
> server for 
> the duration of thier visit.  I used another cookie for this, 
> but it was 
> a hack and I abandoned it in favor of a bigger server.

There's already the ability to add a session prefix code -- see the
SessionPrefix setting.

Unfortunately the adapters don't yet do anything with that prefix code.  It
would be quite easy to modify WebKit.cgi (or the ModPythonAdapter) to use it
to route requests, and a bit harder to modify mod_webkit or wkcgi only
because they are in C, not Python.

- Geoff


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Webware-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-devel

Reply via email to