- From: jesup via GitHub <sysbot+gh@w3.org>
- Date: Thu, 11 Apr 2019 15:26:14 +0000
- To: public-webrtc-logs@w3.org
The point of the overall design for the JS interface was to largely ducktype to WebSockets, so (other than setup code) you can substitute a DataChannel for a WebSocket. Two issues: any code that assumes the default as specified for the last ~6 years might break. (This is mitigated by Chrome and now Safari not following the spec, requiring any user to deal with that.) The other is that it requires an extra step when substituting for a WebSocket. I don't know what's still holding up resolving https://bugs.chromium.org/p/webrtc/issues/detail?id=2276 to get blob support in Chrome; bug was filed in 2013 and was blocked waiting on ndata. (Because the WG decided to reverse course and drop the original in-browser chunking in favor of ndata, which was "going to be available soon".... instead of implementing the original spec and then using ndata if and when it was available) If the DataChannel default changes, any user leveraging the ducktype aspect (at least once issue 2276 is resolved) will need to add a binaryType = 'blob' line. Which is not a big bar, but just what would be required. -- GitHub Notification of comment by jesup Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2170#issuecomment-482161540 using your GitHub account
Received on Thursday, 11 April 2019 15:26:16 UTC