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
then the cache will just slow things down.
Kevin Jones
DevelopMentor
www.develop.com
-Original Message-
From: Ferguson, Doug [mailto:[EMAIL PROTECTED]]
Sent: 31 January 2001 15:35
To: '[EMAIL PROTECTED]'
Subject: session variables in a server farm
Is there an elegant way to implement
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
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
Our application is completely stateless except for login information.
We do load balancing with a hardware load balancer which I believe
is a Foundry Server Iron?
I now considering keep our login state in a stateful session bean(ejb)
And store the home handle to this bean in a session
At 11:16 AM 1/31/01, you wrote:
Our application is completely stateless except for login information.
We do load balancing with a hardware load balancer which I believe
is a Foundry Server Iron?
I now considering keep our login state in a stateful session bean(ejb)
And store the
Ferguson, Doug typed the following on 09:35 AM 1/31/2001 -0600
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
