Hi,
I've been thinking about this a bit more, and I understand why normally
the response.close() should not go to the TCP layer: I'd forgotten all
about request pipelining.
However, in my case, the request has an explicit "Connection: close" header.
Would not this case warrent an immediate shutdownOutput on the
underlying socket?
Regards,
Sebastiaan
P.S.: I really like Tomcat and Comet, so definately good job to you
guys! Please don't read my emails as complaints; I just want to
understand the API better and work with you guys to improve Comet by
reporting possible bugs and sharing the issues I'm having!
Filip Hanik - Dev Lists wrote:
Correct, an asynchronous close doesn't go all the way down to the IO
layer, it just marks the request closed.
remember event.close doesn't mean TCP.socket.close, it means that this
event/request sequence is done
There are still many enhancements to be done to the Comet API, such as
non blocking reads/writes and others, feel free to gather up your
thoughts in a bulleted type email instead of the essays, they are a
little hard to read :)
Filip
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
