RE: In memory session replication, reminder

age- >From: GOMEZ Henri [mailto:[EMAIL PROTECTED]] >Sent: Thursday, March 14, 2002 11:49 PM >To: Tomcat Developers List >Subject: RE: In memory session replication, reminder > > >jtc could became jakarta-tomcat-commons, a repository >of stuff used by tc 3 and tc 4 > >

RE: In memory session replication, reminder

364F 80E6 >-Original Message- >From: Filip Hanik [mailto:[EMAIL PROTECTED]] >Sent: Wednesday, March 13, 2002 9:50 PM >To: Tomcat Developers List >Subject: RE: In memory session replication, reminder > > >>Also, sorry for not mentioning it before (I didn't real

RE: In memory session replication, reminder

>That kind of design would be more interesting. I was probably too harsh in >my response; I just wanted to point out I made a mistake by being that >enthusiastic about it originally. > >I think I'll create a 'cluster' component in j-t-c, as was suggested, and >move the existing cluster implementat

Re: In memory session replication, reminder

> >Also, sorry for not mentioning it before (I didn't really look at the > >details, I have to admit ;-) Too busy :-(), but I have a problem with JG's > >license. Basically, I don't want to create any dependency to it, > >and I don't > >want JG to be part of the TC build process. > > it doesn't ha

RE: In memory session replication, reminder

>Also, sorry for not mentioning it before (I didn't really look at the >details, I have to admit ;-) Too busy :-(), but I have a problem with JG's >license. Basically, I don't want to create any dependency to it, >and I don't >want JG to be part of the TC build process. it doesn't have to be, it

Re: In memory session replication, reminder

> >Well, apparently a lot of people would want that in j-t-c instead, and I > >think they are right. > >j-t-c/cluster should be a good name. > > > >Remy > > Hi Remy, > j-t-c, that refers to Jakarta-tomcat-connectors right? > If jtc is the connectors, from looking at my code, I'm not sure how this

RE: In memory session replication, reminder

t;Sent: Wednesday, March 13, 2002 12:01 PM >To: Tomcat Developers List >Subject: Re: In memory session replication, reminder > > >> >JavaGroups is cool since it is pure, multiplatform Java, although >> >(from what I know) it cannot fall back to TCP when multicast isn&#

Re: In memory session replication, reminder

> >JavaGroups is cool since it is pure, multiplatform Java, although > >(from what I know) it cannot fall back to TCP when multicast isn't > >available, > > JavaGroups is cool, thanks :), and yes, it does support TCP. :)) > > >What I'd like to do at some point is take Filip Hanik's TC4 session > >

RE: In memory session replication, reminder

t have commit privileges. have a wonderful day. Filip ~ Namaste - I bow to the divine in you ~ Filip Hanik Software Architect [EMAIL PROTECTED] www.filip.net >-Original Message- >From: Jason Brittain [mailto:[EMAIL PROTECTED]] >Sent: Monday, March 11, 2002 6:01 PM >To: Tomcat De

RE: In memory session replication, reminder

>> We speak about spread some times ago but the licence wasn't Apache >> at this time, and yes it's another good Broadcast system. >> Good point it support native and java. > >Spread has a BSD license now. Thanks to many ASF members >speaking to the >spread developers and convincing them to switc

Re: In memory session replication, reminder

on 3/12/02 1:08 AM, "GOMEZ Henri" <[EMAIL PROTECTED]> wrote: > We speak about spread some times ago but the licence wasn't Apache > at this time, and yes it's another good Broadcast system. > Good point it support native and java. Spread has a BSD license now. Thanks to many ASF members speaking

RE: In memory session replication, reminder

>If you liked that, also have a look at Spread: > >http://www.spread.org/ > >The messaging engine (daemon) isn't written in Java, but it's very >fast and efficient, and runs on all the popular OSs. The Java clients >connect to it via TCP sockets, so the clients can be pure-Java. The >License is

Re: In memory session replication, reminder

GOMEZ Henri wrote: >>You can start with my doc, there are two references to >>JavaGroups in there >>http://www.filip.net/tomcat/tomcat-javagroups.html >>http://www.javagroups.com/ >> >> >>>- Does it use multicast or others broadcast techniques ? >>> >>Virtual Synchrony and Probabilistic broadcast

RE: In memory session replication, reminder

>From: Remy Maucherat [mailto:[EMAIL PROTECTED]] >I got the classes, and briefly looked at it. I didn't have time to actually >test it, but it looks well worth committing. >My main gripe with the contribution at the moment is that it does not >respect at all the coding style used in the rest of Ca

Re: In memory session replication, reminder

> >From: GOMEZ Henri [mailto:[EMAIL PROTECTED]] > >>Move it out of the core, it adds complexity. Leave/add any hooks you > >>need, but keep the bulk of the code/interfaces out, in a separate > >>module. > >> > >>I would even sugest j-t-c, since it's likely to need some of the > >>things there ( un

RE: In memory session replication, reminder

>You can start with my doc, there are two references to >JavaGroups in there >http://www.filip.net/tomcat/tomcat-javagroups.html >http://www.javagroups.com/ > >>- Does it use multicast or others broadcast techniques ? >Virtual Synchrony and Probabilistic broadcasting on top of IP >Multicasting.

RE: In memory session replication, reminder

>From: GOMEZ Henri [mailto:[EMAIL PROTECTED]] >>Move it out of the core, it adds complexity. Leave/add any hooks you >>need, but keep the bulk of the code/interfaces out, in a separate >>module. >> >>I would even sugest j-t-c, since it's likely to need some of the >>things there ( unix sockets, sh

RE: In memory session replication, reminder

: GOMEZ Henri [mailto:[EMAIL PROTECTED]] >Sent: Monday, March 11, 2002 3:06 PM >To: Tomcat Developers List >Subject: RE: In memory session replication, reminder > > > > > >- >Henri Gomez ___[_] >EMAIL : [EMAIL PROTECTED](. .) >PGP KEY :

RE: In memory session replication, reminder

>Move it out of the core, it adds complexity. Leave/add any hooks you >need, but keep the bulk of the code/interfaces out, in a separate >module. > >I would even sugest j-t-c, since it's likely to need some of the >things there ( unix sockets, shmem, etc ). +1 -- To unsubscribe, e-mail:

RE: In memory session replication, reminder

: 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 >-Original Message- >From: Filip Hanik [mailto:[EMAIL PROTECTED]] >Sent: Monday, March 11, 2002 5:57 PM >To: Tomcat Developers List >Subject: RE: In memory session replication, reminder

RE: In memory session replication, reminder

12:07 PM >To: Tomcat Developers List >Subject: Re: In memory session replication, reminder > > >On Fri, 8 Mar 2002, Remy Maucherat wrote: > >> I'll try to look at it this time. >> >> IMO, the Cluster feature in Catalina either needs a maintainer >or needs to

RE: In memory session replication, reminder

364F 80E6 >-Original Message- >From: Filip Hanik [mailto:[EMAIL PROTECTED]] >Sent: Friday, March 08, 2002 7:31 PM >To: [EMAIL PROTECTED] >Subject: In memory session replication, reminder > > >Hi Henri, Remy and all other developers. >I just wanted to send you a reminder since

Re: In memory session replication, reminder

On Fri, 8 Mar 2002, Remy Maucherat wrote: > I'll try to look at it this time. > > IMO, the Cluster feature in Catalina either needs a maintainer or needs to > go. The better option would be to find a maintainer, obviously ;-) IMHO the better option will be: both :-) Move it out of the core, it

Re: In memory session replication, reminder

> Hi Henri, Remy and all other developers. > I just wanted to send you a reminder since I haven't received any feedback > on the > clustering code I sent you. > > There are already people using the code, but it is almost impossible for me > to maintain and improve this codebase if it remains outsi

In memory session replication, reminder

Hi Henri, Remy and all other developers. I just wanted to send you a reminder since I haven't received any feedback on the clustering code I sent you. There are already people using the code, but it is almost impossible for me to maintain and improve this codebase if it remains outside the Catali