Re: [LONG TERM PLAN] Proposed Architecture for Tomcat.Next Servlet Container

[James Duncan Davidson <ja...@eng.sun.com>]

on 12/30/99 3:44 PM, Assaf Arkin at arkin@exoffice.com wrote:

> What happened to Servlet chaining?

It was an ugly hack that we did in JWS. It's ugly because it was
non-deterministic. A servlet could not reliable figure out if it was a
"producer" servlet or a "filter" servlet. As well, since all the headers of
the response of the producer were slammed into the request header hashtable,
the filter *had* to propogate headers forward to it's response in order to
make the application work correctly (think set-cookie).

The functionality was useful, but the implementation didn't even approach
grace.

James Davidson                                     duncan@eng.sun.com
Java + XML / Portable Code + Portable Data                 !try; do()