Return-Path: Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 18348 invoked from network); 3 Jan 2000 00:34:58 -0000 Received: from unknown (HELO titan.exoffice.com) (root@207.33.160.98) by 63.211.145.10 with SMTP; 3 Jan 2000 00:34:58 -0000 Received: from exoffice.com (dialup-209.245.140.125.SanJose1.Level3.net [209.245.140.125]) by titan.exoffice.com (8.9.3/8.9.3) with ESMTP id RAA20131 for ; Sun, 2 Jan 2000 17:28:37 -0800 Message-ID: <386FC428.CAD1E643@exoffice.com> Date: Sun, 02 Jan 2000 16:33:28 -0500 From: Assaf Arkin Organization: ExOffice X-Mailer: Mozilla 4.5 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: tomcat-dev@jakarta.apache.org Subject: Re: [LONG TERM PLAN] Proposed Architecture for Tomcat.Next Servlet Container References: <38691FD0.ACA719C@exoffice.com> <38693E55.B129B304@apache.org> <38695673.A8EEBFB7@exoffice.com> <3869FC57.8FDB8CF3@apache.org> <386B8A15.51576618@mytownnet.com> <386BEA56.E0E85D5B@apache.org> <386C0555.AFE401F6@adelphia.net> <386CA904.2B4CFC1F@apache.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Craig has an interesting idea, of running Servlets using Interceptor. Tomcat will use a default container through the Interceptor API, but you can plug in a different container. In that case, c) is needed. arkin Stefano Mazzocchi wrote: > > Ray Racine wrote: > > > > Stefano Mazzocchi wrote: > > > > > > > > So, the interceptor pattern is composed by > > > > > > a) Monitor (symmetric): performs side actions while nothing is modified. > > > This is automatically transparent to all and servlet operation is > > > automatically portable since nothing is modified by its presence. > > > > > > b) Filter (asymmetric): performs request filtering. > > > > > > c) Servlet: generates a response, given a request. > > > > > > Decomposed in these atomic subpatterns, I see no problems for monitors > > > at all, but I do see problems for the "filter" and "servlet" > > > subpatterns. > > > > c) Seems redundant given the availability of b). We already have a servlet > > response generator available "within" the wrapping interceptor. Tomcat. > > > > In other words, instead of having the interceptor generate a response, > > leverage the fact we have a servlet engine available. Use the > > Filter/Rewrite functionality in the interceptor to filter/rewrite the request > > to invoke a specific servlet(s) in Tomcat to generate whatever response is > > required. > > Good point. This is part of what I was leading at. > > I must be honest, I don't like c) operation, but I don't see the pattern > globally enough to propose a better solution. > > Craig? Assaf? can we get rid of c) without destroying the whole thing? > > -- > Stefano Mazzocchi One must still have chaos in oneself to be > able to give birth to a dancing star. > Friedrich Nietzsche > -------------------------------------------------------------------- > Come to the first official Apache Software Foundation Conference! > ------------------------- http://ApacheCon.Com --------------------- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org > For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org