>You're manager may be an idiot on this... depending on platform, settings >etc. Most importantly, everything you put in the session must be >serializable in order for the servers to pass around the session data.
>I would also be interested in knowing why, in your case, server affinity >would be such a bad idea? If server affinity is a bad idea, why not >upgrade your server to something that can handle session attibutes better >in a clustered environment? Some platforms don't allow sessions to be available to each machine in a cluster, most notably the web "platform" (I use the term loosely) found to be in widespread use by a certain large unnamed software company in the northwestern U.S. In that case, using sessions can be an issue. You can have "sticky" connections on your load balancer, but this can cause some pretty asymmetrical loads if your site has a large number of users behind a NAT, for example. Of course, this isn't an issue for Tomcat sessions (and probably every other J2EE container out there). My $0.02 Brantley Hobbs --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
