>Hi Remy,
>thanks for getting back to me.
>
>>Yes, why not.
>>Note that the feature is:
>>- a bit redundant with JK/JK2 load balancing, so it's not my 
>top priority
>>personally
>>- currently in alpha/unsupported status
>
>I'm not sure about the JK/JK2 load balancing feature, but from 
>the name of
>it, I don't think they are redundant, they are two pieces that 
>complete the
>puzzle. See my implementation only does session replication, 
>nothing else.
>If you have JK/JK2 do loadbalancing between the different 
>tomcat servers and
>session replication, then you are all good to go. A complete cluster
>solution.

LoadBalancing + SessionReplication are not redundant, they are the 
2 major piece of Failover/Recovery, and I'll be more than happy to
see that piece of code.

I proposed sometimes ago to add such functionnality in jk/jk2, by
extending jk protocol to forward  to web server, http answers and
also ALL session ID + session DATA (when there is an update).

In recover mode, a backup tomcat could then receive REQUEST AND 
SESSION ID/SESSION DATA which where produced previously by master
tomcat.

>Where do I look at the JK/JK2 code?

jakarta-tomcat-connectors

>And where/to who do I send my files to be submitted to CVS?

Send it to the list, we take all a revue and commit it if
everybody agree :)

I'll take a definitive look at it

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to