Okay, now I'm a little fuzzy (fuzzy logic?) on your filter thing.
Do you mean filters in what I consider the standard sense of
piping bytes through various input/output streams and encoders,
or are you talking about something else? If not too much
trouble, would you give a concrete (i.e., code) example?
Cheers!
Mark
----- Original Message -----
From: "Nic Ferrier" <[EMAIL PROTECTED]>
Sent: Thursday, April 19, 2001 1:53 PM
> Because you don't really understand what a filter is. It's not
a
> servlet chaining system it's much more than that.
>
> A filters can adapt the entire environment that the target
recieves,
> they can do that in a completly modular way and they do it
without
> interfering in the syntax of your page invocations.
>
> For example:
>
> - you could have a filter handle multipart submits and present
them
> to the target in a sensible way (maybe through some pre-defined
> attribute or an additional method)
>
> - a filter could extract elements from a database query leaving
the
> results in a hash on the request attributes, or directly
accessible
> through an extended request object
>
>
> Filters can directly take over from servlets in an MVC model.
>
> If we find a way of declaring dependancies between filters and
JSP
> pages (or whatever display medium is being used) then that will
be a
> further step in the right direction.
>
>
> Nic
___________________________________________________________________________
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
