+1 I think we should tag the code with jk_1_4 ( considering the jk that was included with 3.1 == jk1.1, etc ). It seems jk_1_4 will work with 3.3, 4.0.x and 4.1 ( and the C code can be used for 3.2.x for bug fixes ).
Regarding jk2, I'm still working, the current strugle is with the unix domain sockets ( since JFC commited the jk implementation, and I promised I'll do the java side ). I did some more changes in mod_jk(2) config, now seting "JkWebapp" in a Location context works for virtual hosts and almost everything else. I do plan few more config changes - automatically restrict WEB-INF, etc, and I want to get at least basic info out of the status worker. On the java side we have a first version, but I still have to integrate it with either the interceptor/connector, or ( assuming everything works as it seems ) in JkServlet ( using what I proposed last year, i.e. web.xml/'standard' servlets + 'trusted apps' + a bit of magic). Sorry it takes so long, but I have a lot of other work to do... Costin On Thu, 3 Jan 2002, Kevin Seguin wrote: > there was a thread a couple weeks ago regarding what to do with j-t-c and > tomcat 4.0.2. i believe it was decided that the 4.0.2 release would contain > the same jars from j-t-c (tomcat-ajp.jar, tomcat-util.jar) as 4.0.1 did. > > well, i just did some quick tests with the 4.0.2-b1 dist and the head of > j-t-c, and all seemed to be in working order. > > so, i think it might be a good idea to try to release the latest stuff from > j-t-c with 4.0.2 for a couple of reasons: > > *) if we release and tag j-t-c along with jakarta-tomcat-4.0, i think > it'll > be easier to do maintenance, fix bugs, etc.. i'm not only talking > about > the java code in j-t-c, but also the c code. > *) there have been some bug fixes in j-t-c since 4.0.1 -- these may as > well > be released :) > > thoughts? > > -- > 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]>
