tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 53391] CometEvent.close() doesn't close socket when called from different thread
Date Mon, 11 Jun 2012 11:28:32 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=53391

--- Comment #2 from Mark Thomas <markt@apache.org> ---
I'm not convinced that the behaviour you are seeing is a bug.

Currently:
a) END if called from within event() closes the connection
b) END if called from a separate thread does not close the connection

Essentially, the difference is that b) supports HTTP keep-alive whereas a) does
not. While this report suggests the b) is incorrect, I am leaning towards a)
being incorrect.

Since from the client point of view, this is just an HTTP connection (the
client may have zero knowledge of the Comet processing at the server end) then
I see no reason not to support keep-alive. END should finish the response but I
see no need for it to force the closing of the connection.

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message