- From: <bugzilla@jessica.w3.org>
- Date: Thu, 12 Jun 2014 15:54:56 +0000
- To: public-webrtc@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25102 --- Comment #4 from Kiran <kiran.guduru@samsung.com> --- We might have followed the WebSockets in some scenarios, but not in all scenarios. There are some differences which I found between WebSockets and DataChannel. The following is one, we may find some more also. 1. In case of WebSockets "closing" should start only after sending all the pending buffers. "The close() method does not discard previously sent messages before starting the WebSocket closing handshake — even if, in practice, the user agent is still busy sending those messages, the handshake will only start after the messages are sent." DataChannel.close() has not specified any information of this kind. Perhaps this might be the reason websockets are not throwing exception for send() in 'closing' state, but I am not sure. In case of DataChannels, I don't find any use for incrementing bufferedAmout value after closing. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
Received on Thursday, 12 June 2014 15:54:58 UTC