John Henry Xu wrote:
Here is Rick's original requirement,
I have an odd requirement where this internal application should
only be used by one valid user(one session) at a time. (The data
being worked with in the application would require so many locks
that's it just easier to restrict it to one user).
Only if one session ends, another connection can establish connections,
always you have only one user connect to data. It doen't matter if
web-browser performing keep-alive or not. If web browser droped the
connection, this session ends and original user drops connection. Another
new (only one) session will begin. So still only one user connects. So
this answered your posts below:
I'm not sure that disallowing additional _connections_ is a good idea; I
think you'd want to be able to display a page saying "Hey, I'm not
available right now, please try later" or something. I'd think it would
be important to allow multiple connections but still let only one user
be "logged in" at a time.
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
