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*
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 sess
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
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 mecha
on 5/7/01 5:30 AM, "GOMEZ Henri" <[EMAIL PROTECTED]> wrote:
> Did you consider use the Multicast cluster with
> Spread (http://www.spread.org/) ?
Spread kicks ass and is the "Right Way ". The license sucks balls.
Sending the authors *gentle* thoughts about how you would like to use their
softw
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
To summarize, I see the following issues needing to be considered
and resolved for distributed sessions:
- Management of session ID/request redirection,
- Architecture of Manager/Store/Cluster interfaces.
I made a few points on the architectural front in my previous post.
For request/ID managem
Did you consider use the Multicast cluster with
Spread (http://www.spread.org/) ?
-
Henri Gomez ___[_]
EMAIL : [EMAIL PROTECTED](. .)
PGP KEY : 697ECEDD...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
Kief Morris wrote:
>
> Bip, thanks for kick-starting this discussion, sorry I've taken a while to look
> at it.
>
> [...]
If you(or anyone else) wants to play around with the highly experimental Cluster
add this right under your in server.xml
..bip
Kief Morris wrote:
>
> [...]
>
> This is one possibility, but if this technique is used, I'm not sure there's
> a real need to distribute the sessions at all - the redirector can simply
> send the client to the Tomcat instance which holds the session locally.
Well that's true if the machine tha
Bip, thanks for kick-starting this discussion, sorry I've taken a while to look
at it.
>> One thing I haven't figured out is this. Say I replicate a
>> Session to another machine and succefully install it in the manger, if
>> I connect to that machine and tries to resume that session it doesn't
I would think that, if it already existed, the API described by
the new JSR 107
http://java.sun.com/aboutJava/communityprocess/jsr/jsr_107_cache.html
would be strongly considered as the basis for a distributed session
manager. Any design made now ought to have an eye on going over to that
API in
I started looking at how to implement a DistributedManager and as I see it the
best way to do this is to use MulticastSocket. So I started to look at how to
implement it using MulticastSocket and started thinking about including that in
a Cluster package. So you configure a package from within Se
13 matches
Mail list logo
