>I'd like to see development of a general server-side Java filter
>mechanism. There are some great advantages to chaining, but
>shoe-horning servlets into the role where a filter belongs isn't
>long-term viable.
>
>-jh-
Amen to that! Filtering response data into a request object is a big fat
hack!
The Servlet API needs a built-in mechanism for setting the filter for a
response object.
Chaining is a hack way of transparently putting some response data into a
request where only some of the fields are valid (only headers and the
InputStream are truely valid since they are the only fields explicitly
settable in the response) and where some of the info from the orignal
response is lost (such as response code for which there is no equivalent
field in the request).
-Spike
-----
Spike Washburn
IBM WebSphere Application Server
Internet E-mail: [EMAIL PROTECTED]
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
