According to Jon Smirl:
> I received the following mail asking for chunked-encoding support. Does
> anyone know an example of a publically available client that makes chunked
> requests? Supporting this is probably going to require changes to the C and
> Java portions of Jserv. I've never encountered a client that made a chunked
> request and I'd like to see one before making any changes.
It's been almost a year ago by now, and the details are escaping me, but
first of all, the document that is referred from your mail already contains
all the answers.
Briefly,
- mod_jserv has to be fixed to allow the chunked stream to either be
dechunked or passed through.
In the first case, the rest is totally transparent, in the second, it may or
may not be transparent and there's a conflict with at least JSDK up to 2.1
that don't address that issue at all, presuming that the input stream is
already dechunked (or rather silently ignoring the possibility of the input
stream being chunked).
- If it would be possible to pass through the chunked stream, the presence
of a header "Transfer-Encoding: chunked" is an indication of the fact that
the stream is indeed chunked. To handle that case, I wrote a couple of
classes, find them @ http://freehold.crocodile.org/~vt/jukebox/, feel free
to tear them off and use.
- As for output stream, noone prevents you from forcing the
"Transfer-Encoding: chunked" header and writing the output through the
ChunkedOutputStream, unless mod_jserv or Apache interfere in some way.
Bottomline, I don't remember what it took me to do, but I was able to
operate with the chunked streams in both directions - in and out.
Unfortunately, the code is quite unreachable at the moment ;/
> Jon Smirl
--vt
--
----------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
