Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 83745 invoked from network); 5 Apr 2002 03:03:01 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 5 Apr 2002 03:03:01 -0000 Received: (qmail 2665 invoked by uid 97); 5 Apr 2002 03:03:04 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 2639 invoked by uid 97); 5 Apr 2002 03:03:03 -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 2628 invoked from network); 5 Apr 2002 03:03:03 -0000 Message-ID: <017e01c1dc4e$8250ae90$ec66a8c0@bbarkerxp> From: "Bill Barker" To: "Tomcat Developers List" References: Subject: Re: Coyote: replacing Processor with ProtocolHandler Date: Thu, 4 Apr 2002 19:03:48 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Archived: msg.XXqwvWLA@scooby X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N It's fine with me. I also have a slight preference for the 33 ThreadPool, but it's not a big deal either way. If we're going to move the socket handling into o.a.c.http11, what about importing o.a.t.util.net? It should mean that Tomcat 4.x should be able to get PureTLS support fairly cheaply. ----- Original Message ----- From: To: Sent: Thursday, April 04, 2002 3:25 PM Subject: Coyote: replacing Processor with ProtocolHandler > Hi, > > In order to merge the connector-related code in Coyote and jk, I need > a different abstraction. Processor takes InputStream/OutputStream params, > and assumes the connector will listen on the port, etc. > > The problem is that it doesn't map to things like JNI and is hard to > abstract things like UnixSocket. > > I would like to replace it with a similar interface, ProtocolHandler, > which is stateless ( Servlet-like ) and will just have a init()/destroy() > method, letting the protocol deal with the threads. > > It's easy to implement it in http11 - this is duplicated in the 33/40 > versions. I would prefer to use the 33 thread pool from util, but > I'm ok with the code used in 40 ( or I can implement both, with an > option ). > > Also, I would like to reduce/eliminate the use of Socket and the other > dependencies between Coyote and the protocol impl ( it is supposed > to abstract it, but there are few details.. ) > > Remy, Bill - is it ok ? > > Costin > > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: > -- To unsubscribe, e-mail: For additional commands, e-mail: