- From: jesup via GitHub <sysbot+gh@w3.org>
- Date: Sat, 02 Sep 2023 02:00:44 +0000
- To: public-webrtc-logs@w3.org
As much as it pains me as the person who wrote most of the spec, 10 years of foot dragging has made this largely a moot point. The original design was quite reasonable and made sense at the time, especially since we envisioned being able to have applications based on WebSocket be easy to transition to DataChannels. WebTransport (once Safari supports it...) is a better replacement for WebSockets, though it is not API-compatible with WebSockets or DataChannels, and like WebSockets it's server-client only. DataChannels can be server-client, or peer-2-peer, so it provides important abilities the other 2 don't. It probably makes sense to change the default at this point. It is too bad Chrome didn't at least require a type of arraybuffer to be set instead of implementing a default different than the spec, but again, that's history now. If effort is going to be expended now to improve the API, it would be find ways to layer Streams on top of DataChannels. They weren't ready when this was designed over a decade ago. -- GitHub Notification of comment by jesup Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2170#issuecomment-1703643092 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 2 September 2023 02:00:46 UTC