Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
At 11:36 AM 8/16/01 -0700, Keith Irwin wrote:
>Is there any way to prevent sessions from being saved to disk?
Not that I know of. It wouldn't be hard to write a session store that
didn't save sessions -- just take SessionMemoryStore.py and strip out the
loading and saving code.
Do you have some particular reason you don't want to store sessions to
disk? Obviously, it's usually a good idea to save the sessions so that you
can restart the app server without losing information...
- Geoff Talvola
From: Keith Irwin <kirwin14@ho...> - 2001-08-16 23:56:23
> >Is there any way to prevent sessions from being saved to disk?
> Not that I know of. It wouldn't be hard to write a session store that
> didn't save sessions -- just take SessionMemoryStore.py and strip out the
> loading and saving code.
> Do you have some particular reason you don't want to store sessions to
> disk? Obviously, it's usually a good idea to save the sessions so that you
> can restart the app server without losing information...
The reason is because I push objects into the session which seem to be
not found when the session is loaded back in (or which cause an error
when the SessionSweeper comes around). Somewhere else, someone
mentioned that the CVS version solved this problem, so if I can get
through to CVS from behind a firewall, I'll try that.
Also, I'm storing classes I generate on the fly, and I'm not sure that
they'll continue to exist if swapped out.
Finally, I DON'T want session information between restarts of the
server, at least not for now. I could see that it's useful, especially
if you'd like to cron a job to restart the server once in a while just
for clean up, and also for some future load balancing. Anyway, I was
hoping that I could turn it off, leave it dynamic.
If it's not part of the options for Webware, I can go in and "fix" it
myself, if necessary (or even if temporarily for development). On the
other hand, if setting the time-to-disk to zero does it, that would be
nice to know as well.