> It is pretty unlikely that you will be able to manage chunked encoding at
the
> user level if your servlet container does not do it for you (in which case
it
> would be supported automatically). The ServletOutputStream implementation
> actually used is normally intimately connected to the internals of the
server
> you are running inside.
>
Yes, it's a gap in servlet API specification. If you are going to distribute
your servlet, you have no idea what servlet engine will be used and you have
no way check, will it support chunked encoding or not. Actually, current
servlet specification is pretty clear regarding this issue. Servlet engine
provides plain stream for yours output, and it's a servlet implementator
responsibility to add any encoding over it. Actually, a servlet engine
provider has no idea how are you going to use chunked encoding, when chunk
should be finished, and send to client. I think, some helper classes can be
added to servlet.util package to help a servlet developer implement chunked
encoding for particular needs.
Dmitry.
___________________________________________________________________________
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
