I don't know anything about your app, but I would simplify the problem by
keeping session affinity with a single server, i.e. load-balance at the
session level rather than at the request level. If you don't tie a session
to a single server, you aren't just looking at unitary login problems but
also at server-side session cache consistency issues.
If you really need failover, though, you probably have to solve those
problems anyway.
At 10:35 AM 1/31/01, you wrote:
>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.
-------------------------------------------------------------
Dennis Doubleday email: [EMAIL PROTECTED]
yourfit.com, Inc. web: http://www.yourfit.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
