Author: remm
Date: Thu Jan 23 14:42:21 2014
New Revision: 1560702
URL: http://svn.apache.org/r1560702
Log:
- Call onClose before actually closing anything (sending a close message closes
the endpoint).
- If onClose throws an exception, call onError.
- After using a blocking send, clear the
On 23/01/2014 14:42, r...@apache.org wrote:
Author: remm
Date: Thu Jan 23 14:42:21 2014
New Revision: 1560702
URL: http://svn.apache.org/r1560702
Log:
- Call onClose before actually closing anything (sending a close message
closes the endpoint).
-1 (veto) for a specification violation
2014/1/23 Mark Thomas ma...@apache.org
- Call onClose before actually closing anything (sending a close message
closes the endpoint).
-1 (veto) for a specification violation
Section 2.1.5 requires that:
the implementation must attempt to send the websocket close frame prior
to calling
On 23/01/2014 15:01, Rémy Maucherat wrote:
2014/1/23 Mark Thomas ma...@apache.org
- Call onClose before actually closing anything (sending a close message
closes the endpoint).
-1 (veto) for a specification violation
Section 2.1.5 requires that:
the implementation must attempt to send
2014/1/23 Mark Thomas ma...@apache.org
I'd need to go back and check the archives but the I think the
expectation from the EG was that onClose() would be used to clean up
resources rather than anything else.
It is always possible that I have misunderstood the intention of the
spec here but
