Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org Received: (qmail 35197 invoked by uid 500); 24 Jun 2001 01:17:44 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: tomcat-dev@jakarta.apache.org Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 35187 invoked from network); 24 Jun 2001 01:17:43 -0000 Date: Sat, 23 Jun 2001 18:20:36 -0700 (PDT) From: cmanolache@yahoo.com X-Sender: costin@d-ucup02-251-93.Eng.Sun.COM To: tomcat-dev@jakarta.apache.org Subject: AjpXXPacket Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: localhost.apache.org 1.6.2 0/1000/N Ok, first change. Would it be ok with you if I just drop Ajp14Packet in jk, and use the "plain" ByteChunk, plus a Ajp14Marshall to implement the marshaling on top of ByteChunk ? The idea is that ( someday - soon I hope ) ByteChunk will be able ( via a Liaison or the o.a.t.util.compat ) to interoperate with nio, and I want to keep all communication around the buffers ( to make my life easier when I do that ). It would also help simplify the code. Another issue ( I already mentioned it ) - can we make Ajp14 independent, and remove the Ajp13 code from j-t-c/../tomcat33 ( the implementation from the main tree will remain and be used until Ajp14 is ready ) ? I'm now able to authenticate, there are few problems after that - but I hope tommorow I'll be able to use Ajp14 for most things. It's looking very good ( I still can't believe how easy it was to build ! ) Costin