I added the code to JservConnection.java that tracks Content-Length and
insert an EOF when neccessary. A parallel to this would be to make chunked
encoding transparent by tracking it in the Java app.
Do the chunked headers appear in the servlet input stream giving the servlet
writer a chance to decode them? I don't have a client that generates chunked
requests so I can't look and see. I'm downloading Jukebox currently at a
snail's pace.
This seems to imply that JServ used to track content-length EOF and it was
removed:
----------------------------------------------------------------------------
-------
Re: WHY??? posted by Michal Mosiewicz on 05/23/99 20:39
Ed Korthof wrote:
> [...]
> This hasn't nothing whatsoever to do with JServ, and everything to do with
> Apache and RFC 2068.
Believe me I'm pretty familiar with this RFC, and I know that there are
two methods of dealing with end of input streams: content-length and
chunking. Current JServInputStream deals only with the first one becouse
it was probably simpler. So - this specific code was actually used to
make the implementation simpler. Right?
My intention was not to make any noise about it. But AFAIK somebody
proposed to remove this chunk-blocking code. Actually it's not enough to
remove it. That's all. Maybe my english is that poor that I'm hard to
understand.
BTW - I'm finising my implementation of persistent protocol and I've
already rewritten JServInputStream and got rid of this feature. Now I'm
testing this thing... looks promising. :-)
----------------------------------------------------------------------------
----------------------------------
Jon Smirl
[EMAIL PROTECTED]
--
----------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
