This code looks like it's on the right sheet of music. :-) I only read the
message, though.

Use of this approach is subject to my final comment, which boils down to, be
aware of what your servlet container is doing for you already.
Transfer-codings are properties of the message and not of the message
payload - they are things that the HTTP layer does to ensure safe
transmission of the message - and strictly speaking (IMO) servlets proper
shouldn't have to deal with them. However, if your servlet container doesn't
do this for you then the servlet pretty much must.

But I would also still be cognizant of the possibility that if the servlet
container is not HTTP 1.1 compliant in this regard, that if your servlet is
doing chunked transfer-coding don't necessarily assume that the container
will cooperate, recognise what you're up to, and keep the connection open
for you. When I say "container" in this sense I mean the server as a whole -
the thing which handles both the servlet spec and the HTTP spec.

And if the browser on the other end is HTTP 1.0 then don't even bother. :-)
You need to detect that first.


> -----Original Message-----
> From: Jeremias Maerki [mailto:[EMAIL PROTECTED]
> Sent: April 16, 2002 3:12 AM
> Subject: Re: Omitting content length
> There was a recent post on chunked transfer. I haven't checked it out,
> but it might help you.
> Cheers,
> Jeremias Märki
> Postfach 3954 - Rhynauerstr. 15 - CH-6002 Luzern
> Tel. +41 41 317 2020 - Fax +41 41 317 2029
> Internet

Reply via email to