reason its in the spec is so that hardware load
balancers
can map sessions back to the originating machine.
All load balanceres I've dealt with certainly can be configured to
use an arbitrary cookie/URL pattern to manage sticky sessions.
--
Stefan Bethke <[EMAIL PROTECTED]>
Tallenc
JSESSIONID."
I'd like to understand the rationale for this requirement. If the
container manages the session, why would an application care about
the actual mechanism used to track the session? Why can this not be
made configurable?
Thanks,
Stefan
--
Stefan Bethke <[EMAIL PR