tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Mazzocchi <stef...@apache.org>
Subject Re: [LONG TERM PLAN] Proposed Architecture for Tomcat.Next Servlet Container
Date Fri, 31 Dec 1999 13:00:52 GMT
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.
<stefano@apache.org>                             Friedrich Nietzsche
--------------------------------------------------------------------
 Come to the first official Apache Software Foundation Conference!  
------------------------- http://ApacheCon.Com ---------------------



Mime
View raw message