A must read from Filip ;)
http://www.theserverside.com/resources/article.jsp?l=Tomcat
-
Henri Gomez ___[_]
EMAIL : [EMAIL PROTECTED](. .)
PGP KEY : 697ECEDD...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
--
Bip Thelin typed the following on 04:06 PM 5/6/2001 -0700
We also need to answer the question of the request life cycle: the
DistributedManager needs to know when a request begins and ends.
At the beginning, it must lock the session to prevent other Catalina
instances from using it in
Kief Morris wrote:
[...]
My point is that the Manager/Cluster needs to know when the session is in
use by another instance of Catalina. A locking mechanism must be
implemented by the Cluster (or whatever) to prevent a session from being
used by multiple instances at once. This mechanism
On Mon, 7 May 2001, Bip Thelin wrote:
[SNIP]
Do we really need to lock a session for each request and then
replicate it? Sorry I might be confused, you mean a request for a
session or a request as in generating a new request object(http
request). If we assume that a session is only in
Craig R. McClanahan typed the following on 11:18 AM 5/7/2001 -0700
An interesting question is, how do you detect when a session has been
changed? Obviously, you can detect setAttribute/removeAttribute, but
what about changes to the *internal* state of the attributes themselves
that the session
On Mon, 7 May 2001, Kief Morris wrote:
Craig R. McClanahan typed the following on 11:18 AM 5/7/2001 -0700
An interesting question is, how do you detect when a session has been
changed? Obviously, you can detect setAttribute/removeAttribute, but
what about changes to the *internal* state
