forgot to mention, that implementing a hard coded member layer using straight tcp should be pretty easy. just implement the member ship service interface, and you will be good to go
Filip ----- Original Message ----- From: "Filip Hanik - Dev" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Tuesday, July 13, 2004 12:51 PM Subject: Re: Session Replication w/o Multicast > yes, a guy posted a patch on this mailing list a while back, > where you can predefine your members(hardcode them into server.xml). > I am superbusy right now so I have not had time to incorporate those. > So that would be direct tomcat to tomcat replication > > Not sure why you must have a load balancer that supports multicast, should not have > anything to do with it. It is the > switch/hub/router that your tomcat servers connects into that should support > multicast > > > > Filip > > ----- Original Message ----- > From: "Jeremy Nix" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Tuesday, July 13, 2004 12:22 PM > Subject: Session Replication w/o Multicast > > > > Is there currently a way of replicating session information across > > multiple tomcat nodes without multicasting? If not, has any extended > > the Tomcat API to support this? The reason I ask is because we are > > using a hardware load balancer, and it does not support multi-casting. > > One thought is that we could upgrade our hardware to a load balancer > > that supports this (not sure one even exists), but I'm sure that there > > are other means of performing replication besides multicasting. Using > > a database as the session persistence layer is one thought. Direct > > tomcat node to tomcat node in memory session replication is another > > thought. > > > > Just thought I'd see what ideas/solutions are out there. > > > > > > _________________________________ > > Jeremy Nix > > Senior Application Developer > > Southwest Financial Services, LTD. > > (513) 621-6699 x1158 > > www.sfsltd.com > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
