> -----Original Message----- > From: news [mailto:[EMAIL PROTECTED]] On Behalf Of Costin Manolache > Sent: Friday, October 04, 2002 11:13 PM > To: [EMAIL PROTECTED] > Subject: RE: cvs commit: > jakarta-tomcat-connectors/jk/native2/common jk_wo rker_ajp13.c > > > Mladen - time for a jk2.0.2 :-) ? >
Why 2.0.2, did I miss the 2.0.1 ? > I think this was a serious bug - if Nacho confirms the other > tests are passing, we need to push it into a milestone. > I'll do the tests on my side. > As a note: breaking the ajp connection on error is IMO the > best solution for now. If we start doing strong > authentication ( i.e. the > ajp extensions that Henri proposed ) - then it may be > expensive, and we should explore sending an error packet and > ignoring all further incoming messages from tomcat. The java > side should also check available() before sending any > message. That will still avoid the roundtrips. > That convince me even more that we need a constant service channel between the TC and a connector, to be able to deal with the asnyc events on both sides. I would like to see something like that in 2.1 As for the release, I was trying to push one even before your ajp bugfix, so lets go for it. Can we make some STATUS file explaining bug fixes since 2.0.0? MT. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
