typo, if anyone read it, I meant IPV6 :)
PK
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter,
Peter Kennard wrote:
> In some sense yes, but then almost all uses of HTTP are doing this to
> one extent or another because initially HTTP was so shallowly
> conceived.
Actually, I completely disagree. I feel that HTTP has withstood the test
At 04:53 3/5/2007, you wrote:
Peter Kennard wrote:
At 23:07 3/4/2007, you wrote:
But since you can't send the response without finishing the
reading of the input stream - the entire question doesn't seem to make sense.
If the input pipe is slow (ie: cellphone with slow pipe) and you
are sendin
Peter Kennard wrote:
At 23:07 3/4/2007, you wrote:
But since you can't send the response without finishing the reading of
the input stream - the entire question doesn't seem to make sense.
If the input pipe is slow (ie: cellphone with slow pipe) and you are
sending a transaction where the fir
At 23:07 3/4/2007, you wrote:
But since you can't send the response without finishing the reading
of the input stream - the entire question doesn't seem to make sense.
If the input pipe is slow (ie: cellphone with slow pipe) and you are
sending a transaction where the first part of it initiate
if available() is accurately suported I guess that does part of the
job, but it still doesn't let you know the last chunk you read was
the last one. It is wholly dependent on the higher levels reading an
end tag, which seems like a design mistake instead of getting and
"end of file" or "end of
The servlet API does not expose these details. At best you have the
InputStream to read from. (And use available() if you want to try to
read without blocking (but due to buffering probably won't work anyways))
But since you can't send the response without finishing the reading of
the input st
I guess the general form of this question is, with HTTP1.1 chunked
input, how do I read "a chunk at a time", which requires I know the
length of the chunk before calling "read()" so if I attempt to read
more than the length of the chunk so I can process it immediately
instead of waiting for
Hmm - when reading HTTP1.1 chunked data, is there a way of detecting
reciept of the terminal "0" chunk in a servlet ?
Googling about, Apparently this does not report an EOD "exception"
(as I would expect) because some people have been using post last
chunk data for server internal out-of ban
