- From: Bernard Aboba <Bernard.Aboba@microsoft.com>
- Date: Wed, 25 Jun 2014 21:37:45 +0000
- To: "public-ortc@w3.org" <public-ortc@w3.org>
https://github.com/openpeer/ortc/issues/111
Filed by Bernard Aboba
Section 11.3 of the current editor's draft has:
partial interface RTCDataChannel : EventTarget {
Promise send (DOMString data);
Promise send (Blob data);
Promise send (ArrayBuffer data);
Promise send (ArrayBufferView data);
}
There is a known WebRTC 1.0 implementation bug where send can block for substantial time. However, if this bug is fixed, It is not clear that a Promise is needed. Can we remove this?
[Martin Thomson]
What do you do when your peer's receive window is closed? Wouldn't it be nice to learn when the packets were committed to the network? (Or is this a promise that is fulfilled when the packets are acknowledged?)
[Robin Raymond]
We had used promise for the sake of delivery verification (as well as better 'write driven' streaming) but the issue is that this deficiency in DataChannel is not our "problem" to fix. Justin pointed out that we should request that the original Data Channel spec writers to fix the problem in WebRTC and then we adopt the fix instead of possibly forking our own solution to the problem which might be different than there solution...
Received on Wednesday, 25 June 2014 21:38:13 UTC