>>> Peter Delahunty <[EMAIL PROTECTED]>
17-Aug-00 5:04:18 PM >>>
>I think this is a "shit" way of doing things so i challenge
>anyone here to come up with a better solution using servlets.
>The problem is servlets do not handle piping in the current
>spec !!!
See the latest draft spec.
http://java.sun.com/aboutJava/communityprocess/review.html
But the servlet API is unlikely to ever do precisely what you want to
do - it is request/response based and thus the chain is one whereby
the last link in the chain issues the response for all other members
of the chain.
With *some* servlet engines you could overload the ServletResponse
object that you pass to the RequestDispatcher to return a caching
PrintWriter in the call to response.getWriter() but that seems an
awfull waste of effort.
Why on earth do you want to do this?
There are alternative systems around, based on top of servlets, that
allow you to do this sort of thing.
See the Apache projects: Coccoon and Turbine.
Nic Ferrier
___________________________________________________________________________
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
