Remy Maucherat wrote:
Remy Maucherat wrote:
Filip Hanik - Dev Lists wrote:
flush I can see, but close in a comet I can't, there is no way to
send additional data after close is called, as that is a output
stream close method.
calling close, will/should eventually trigger event(END).
Ok, I will make those changes.
And I don't see any way to do it other than adding a begin and an end
action in ActionCode.
I did it in the NIO connector fairly easily, cause in there the socket
is associated with a key, and the key has several attributes, so I just
told the key to timeout.
But using the ActionCode might be a be better solution, as we can apply
it more easily to all connectors.
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
