>I take a look at code but miss the org.javagroups stuffs, >which cover effective replication. > >- Where could I find it ?
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. see the docs Filip ~ Namaste - I bow to the divine in you ~ Filip Hanik Software Architect [EMAIL PROTECTED] www.filip.net >-----Original Message----- >From: 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 : 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 >> >> >>>> go. The better option would be to find a maintainer, obviously ;-) >> >>I would have no problem maintaining the code :) >> >>>Move it out of the core, it adds complexity. >>>Leave/add any hooks you need, >> >>The current implementation is 4 core classes, it could be 3 if >>we made the >>GenericPrincipal serializable. >>IMHO, the core is already in an outside module. The JavaGroups >>system is the >>core of the clustering and that is completely outside Tomcat itself. >> >>So we are talking about a core implementation of 3 classes, it >>is not more >>complex than that, and these classes you can extend to any >>degree you want, >>ie, you could write a file persistence manager on top of the current >>implementation without any problems. >> >>Have a look at the code and see the simplicity of it. Session >>replication is >>not the complexity, it is the group communication that is, and >>that is why >>the current org.apache.catalina.cluster currently has way to >>many classes in >>the core. >> >>Filip >> >>~ >>Namaste - I bow to the divine in you >>~ >>Filip Hanik >>Software Architect >>[EMAIL PROTECTED] >>www.filip.net >> >>>-----Original Message----- >>>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] >>>Sent: Friday, March 08, 2002 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 >>>> 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 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 ). >>> >>>Costin >>> >>> >>>-- >>>To unsubscribe, e-mail: >>><mailto:tomcat-dev->[EMAIL PROTECTED]> >>>For additional >>>commands, e-mail: >>><mailto:[EMAIL PROTECTED]> >>> >>> >> >> >>-- >>To unsubscribe, e-mail: >><mailto:[EMAIL PROTECTED]> >>For >>additional commands, e-mail: >><mailto:[EMAIL PROTECTED]> >> >> > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
