Is that the way it works in your environment Leon? Its not the way it works here :) Or any other clustered environment I've ever worked in.
I mean, the express purpose of a clustered environment is to distribute load. If a user hits one server for one request, but then upon making the second request that server they hit the first time is loaded down, the whole point of the cluster (ignoring failover and such of course) is to get that user to a less loaded server so that all users have a good response time on average. That's also the reason IBM tells you to keep session small: it has to be replicated across the cluster so that any request can be serviced by any machine in the cluster at any given time. That's not to say you COULDN'T configure things to always direct a user to a given server. But I think that defeats the purpose of such an environment :) -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com On Mon, March 7, 2005 3:05 pm, Leon Rosenberg said: >> Assuming so... in a clustered environment, first of all, >> writing to the file system is generally discouraged practice >> (although it can be done safely, so let's ignore what might >> be best practice for the moment)... but if you do so, since >> the upload may start on one server and then the monitor gets >> executed on any server in the cluster with each subsequent >> check operation, how does that get handled? > > The loadbalancer should send all requests from one user to same server, so > it's not an issue. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
