> CLIENT_DISCONNECT is only used a subtype of ERROR
> and that happens when the socket is closed from the client side
When a client disconnects (i.e. socket is closed from the client
side), I see an END event on both Windows and Ubuntu. I expected an
ERROR event with a subtype of CLIENT_DISCONNEC
Peter Warren wrote:
How do I distinguish between a comet END event generated due to a
client disconnect and an end event generated for some other reason?
I'm using tomcat 6.0.18 with the nio connector. On both windows xp
sp3 and ubuntu 8.10, I'm seeing END events generated when a client
disconn
How do I distinguish between a comet END event generated due to a
client disconnect and an end event generated for some other reason?
I'm using tomcat 6.0.18 with the nio connector. On both windows xp
sp3 and ubuntu 8.10, I'm seeing END events generated when a client
disconnects and for other sit
