Geoff Thorpe wrote:
> The hash-database means the only way to
remove expired sessions is to iterate across the entire database!
Or you maintain an auxillary database that maps the expiry time to a
list of session IDs. This could be a btree (perhaps with a bucket of
session IDs, to avoid dulic
On Thursday 31 Oct 2002 8:56 pm, Bear Giles wrote:
> Edward Chan wrote:
> > The default behavior of server-side session caching is
> > to cache session in memory. This is probably not
> > gonna work very well if there are a lot of connections
> > to the server
> >
> > It says to "open file nam
Edward Chan wrote:
The default behavior of server-side session caching is
to cache session in memory. This is probably not
gonna work very well if there are a lot of connections
to the server
It says to "open file named according to session id".
However, session_id contains non-ascii chars,
