Warren Smith wrote:
> It occurs to me that a file-based session store may present
> these problems
> even with only a single app server and local filesystem,
> since multiple
> threads in the same app server could just as easily interact
> in the ways
> described. I see from the source of SessionF
What if you use the sessionID as a key field in a database and store all
of the session variables in a database.
You could either modify session handler or if you have not witten any
code just implement some sort of self.sessionSave() function that looks
like session.value, but talkes to a db i
Geoffrey Talvola said:
> Warren Smith wrote:
>> The CGI app currently runs on more than a dozen web servers
>> that share the
>> same webspace via NFS. The web servers sit behind an "ip
>> sprayer" (on the
>> outside they appear as a single server). Changing this
>> infrastructure is not an optio
Warren Smith wrote:
> I currently support a legacy web based application that is
> implemented in Python CGI scripts with the session data stored
> client-side
> in hidden form
> variables. Although the session form variables are protected from
> manipulation by a checksum algorithm, this is stil
