And why not works first on a jk api ? I know companies, and some providing clustering/frontal box, who complains since their customers ask them for jk proxing/clustering.
If we could proxy a jk API, may be using full APR, it could be easy for them to connect with Tomcat's using AJP and it will give us a good fundation to see what could be jk3. Notice, I speak about jk3, not mod_jk3 or mod_jk 1.3, but just jk3. The library could be named jk3 or ajp3, whatever and I remember there was some works on it in the past. 2009/3/24 Mladen Turk <mt...@apache.org>: > jean-frederic clere wrote: >> >> Mladen Turk wrote: >>> >>> Rainer Jung wrote: >>>> >>>> Hello, >>>> >>>> I'm thinking about branching JK, so adding >>>> >>>> http://svn.apache.org/viewvc/tomcat/connectors/branches/jk1.2.x >>>> >>>> and initially populate the branch with the contents of the 1.2.28 tag. >>>> >>>> The motivation is to stabilize 1.2 and restrict further changes on 1.2 >>>> to patches only. >>>> >>> >>> No need for the branching thought. >>> Just create jk3 and take a blank sheet of paper :) >>> >> >> This is NOT going to happen. > > I suppose you meant, YOU wouldn't work on it. > > > Regards > -- > ^(TM) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
