On Tue, Jul 29, 2003 at 08:05:57AM +1000, Mike Cannon-Brookes wrote:
> No, the servlet is the dispatcher.
> 
> - Before the request, the filter adds a request attribute to say 'I'll
> handle the clean up'.
> - The servlet runs as normal, except if it finds this request attribute, it
> does not pop the action off the stack, nor clean up the dispatcher.
> - After the request, the filter pops the action off the stack, and cleans up
> the dispatcher.
> 
> Basically, no filter - things work just as they do now.
> With filter, your cleanup is postponed until when you want it (governed by
> your ordering of the filter chain).
> 

This looks like a nice way to solve the issue. I suppose the filter
would be part of the framework, to be installed in the web container if
the user chooses to do so? 

Should be a nice, quick, clean hack. 

[snip to much quoted text - where is your email manners, guys ;)]

//Anders

-- 
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. Anders Engström         [EMAIL PROTECTED]
. http://www.gnejs.net    PGP-Key: ED010E7F
. [Your mind is like an umbrella. It doesn't work unless you open it.]  

Attachment: pgp00000.pgp
Description: PGP signature

Reply via email to