On Tue, 13 Nov 2001, Pier Fumagalli wrote:

>
> So, basically, we have to design a lock/unlock mechanism (that complicates
> stuff). It would be easier to achieve without that requirement... (god knows
> why Danny added it).
>

See the answer I just sent for more details -- not enforcing this
restriction would make the application writer's job basically impossible.
(For example, how do you do "synchronized" locks across multiple JVMs to
avoid simultaneous updates to a session attribute?)

Basically, we're going to want some sort of sticky routing like what JK
already does, but with the added ability to migrate sessions "in between"
requests for load balancing and/or high availability.

>     Pier
>

Craig


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to