> > >there hasn't been done anything on that topic yet ? What's > >the status of > >loadbalacing, either mod_jk or mod_webapp ? > >Is that political due to if loadbalacing is working properly > >there won't be > >any reason to take (buy) anything else than TC ? > > State of the art is that today only mod_jk could > handle load-balancing and only when connected > to Tomcat 3.2.x or 3.3. > > Tomcat 4.0.x support ajp13 protocol, used in mod_jk > but still miss a subtil feature (jvmroute) to be > able to keep the route to the good JVM in > session mode (SessionAfinity). > > But the current refactory of ajp protocol, > under ajp14 in jakarta-tomcat-connectors, will > fix somedays thanks to Costin and Kevin works :))) >
how does the connector set/use jvmroute? i assume there is some sort of cookie magic going on, but after a brief tour of the code, it's not obvious to me how this jvmroute stuff works. it seems to me that tomcat (any version) shouldn't have to have anything to do with setting jvmroute. couldn't the connector be solely responsible for this? the connector could add a cookie to the response, then read this cookie on subsequent requests, and then you wouldn't have to add stuff to servlet containers to handle this. or, i could be totally off base :) -kevin. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
