Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 81510 invoked from network); 10 Dec 2001 05:55:54 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 10 Dec 2001 05:55:54 -0000 Received: (qmail 20380 invoked by uid 97); 10 Dec 2001 05:55:57 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 20363 invoked by uid 97); 10 Dec 2001 05:55:57 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 20352 invoked from network); 10 Dec 2001 05:55:56 -0000 Date: Sun, 9 Dec 2001 21:56:10 -0800 (PST) From: X-X-Sender: To: Tomcat Developers List Subject: Re: [j-t-c] ajp and headaches In-Reply-To: <005c01c18101$2fccb5e0$6401a8c0@C538761B> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Sun, 9 Dec 2001, Remy Maucherat wrote: > > maybe it's just me, but i found trying to follow the java code > particularly > > painful. i realize there is some development and refactoring going on > with > > ajp14 and all, but man!, it ain't pretty in there :) > > As far as the Java portion of the connector is concerned, the code is based > on the current HTTP connector, which I don't think is very good (obviously, > I don't like it at all, I wouldn't be experimenting with rewriting it > otherwise). The tomcat4.0 adapter - yes. The connector code ( low level Request, etc ) are based on MessageBytes, etc. It needs some tunning, but I wouldn't change it without some good reasons. I'm more interested in the low level stuff, and if possible I would like to keep a similar object model on both sides ( it'll help on JNI and in general ). The higher level needs some work... Kevin - if you have time, extracting the mapping out of tomcat4 would help a lot ! Also, for passing the 'route' to the session manager we need a bit of code - we need to first "find" the session manager, then a small piece of code to set the jvmRoute on the request. I know this is not 'refactoring', but problems we need to solve asap. Costin -- To unsubscribe, e-mail: For additional commands, e-mail: