Is there an elegant way to implement session variables in a load balancing
senario? If I understand correcty everything is stored on the
server and a sessionID is store in the users browser so that the
server can look it up. But what happens when the user gets routed
to another server which doesn't have their info stored in the session,
we wouldn't want them to log in again. We though about placing this
info in our ejb layer. But we'd like to not have to do a remote call
just for authentication purposes.
d.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
