We simply stopped using the Session object.
And we manage our own sessions through direct coookie management.
The all thing is only to detect a session is not yet established (cookie
absent or content does not include a session id), assign a new session id,
and store a cookie with that info, somehow.
The pages are not much more complex.
We store two or three heavy used variables attached to the session state in
the cookie itself, and the rest of the state of the session is in the
database back-end, accessed through the session id (a primary key assigned
by the database, by the way).
Quite simple workaround, and we get isolation from the ASP runtime.
We can use round-robin DNS scheme to direct the queries to multiple
machines, each with their own Apache & ASP module. A session lives accross
the different servers as nothing is stored in-memory about the session in
the ASP engine itself. It's all in the cookie or in the DB back-end.
After all, it's far better than the Session() system of ASP.
We are about to switch to PHP, (as soon as we'll get that $*##* Interbase
extension to compile and link in the PHP module under Win32), but it is most
certain we will stick to our own-cookie based system for sessions, even
under PHP.
---------------------------------------------------------------------
Olivier Mascia T.I.P. Group SA
[EMAIL PROTECTED] www.tipgroup.com
Director, Chief Software Architect +32 65 401111
----- Original Message -----
From: "KungFusion" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, July 05, 2000 5:01 PM
Subject: ASP: Session Object workaround
| Is there a workaround that someone has for the Session object? I briefly
| remember someone bringing something up about this..
| Thanks,
| Brian
|
|
