Filip Hanik - Dev Lists wrote:
yes, but to do so, you would be required to pre calculate the content
length for the 2 (or N events), and if the server hasn't responded
(since its async) you can't send the 2nd event as you could start a new
HTTP request on the same connection when there hasn't been a response.
So to open your self up for async push for both client and server, you
omit content length, or set it to an extremely large value.
see where I am getting it?
Yes, I do.
Comet "designers" got the idea too (most likely they want to work
somewhat with proxies), and so Comet must use chunking on input (as any
decent HTTP user agent would do automagically) and output (Tomcat will
do it automagically too). This way it works without breaking the
protocol and without having to compute the total length of the
request/response beforehand. Of course, you can have easy testing of the
code by using (fake) large content-length values like I did, but that's
for local testing only.
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
