3 ms·

> Chrome on Android doesn't either Interesting, do you have a source? Or did you try it? > I am not sure what WebTransport would enable that isn't already pos

> Chrome on Android doesn't either Interesting, do you have a source? Or did you try it? > I am not sure what WebTransport would enable that isn't already possible with current APIs. Unreliable datagrams? WebRTC. Reliable bidirectional communication? WebSockets. WebTransport probably would make some of the usecases easier or more efficient but it's value proposition isn't well communicated or better yet, demonstrated. The article does seem to answer these questions.

strbean 4y ago
Can I Use[1] gives mixed messages on this. Seems like it is either partially supported or fully supported and one of the entries is just misleading? [1]https://caniuse.com/?search=webtransport https://caniuse.com/?search=webtransport
- eis 4y ago
  The information there is indeed incorrect. I have updated my comment accordingly.
eis 4y ago
> Interesting, do you have a source? Or did you try it? https://caniuse.com/webtransport https://caniuse.com/webtransport > The article does seem to answer these questions. Not for me. There's no usecase mentioned that is not possible today unless you count using it from inside a worker as a usecase I guess. I wonder btw why they compare WebTransports datagrams to WebSockets reliable streams. The equivalent to WebSockets would be the reliable Streams API of WebTransport. The issue with Head Of Line blocking can be easily solved by opening multiple WebSocket connections. WebTransport just has that solved instead within the protocol.
- markdog12 4y ago
  > https://caniuse.com/webtransport https://caniuse.com/webtransport Yeah, it seems there's an older entry in there that's confusing. Not sure. > There's no usecase mentioned that is not possible today WebTransport does not really do anything that was previously impossible from an API standpoint, it improves on existing methods. > Head Of Line blocking can be easily solved by opening multiple WebSocket connections. WebTransport just has that solved instead within the protocol. Yes, and solving it within the protocol is simpler and more efficient. > It needs a bunch of examples Agreed, that would be nice.
  - eis 4y ago
    > Yeah, it seems there's an older entry in there that's confusing. Not sure. I have just tried it on Chrome 103 on Android 12 and WebTransport worked. The information on caniuse.com is indeed incorrect. > WebTransport does not really do anything that was previously impossible from an API standpoint, it improves on existing methods. Yup, that's why I want to see it widely supported. Any simplification is good for the web. Though WebTransport unfortunately does not improve on every aspect of the existing APIs. It also has limitations that WebRTC does not have like P2P or easily piping media for using in MediaStreams.

strbean 4y ago

Can I Use[1] gives mixed messages on this. Seems like it is either partially supported or fully supported and one of the entries is just misleading? [1]https://caniuse.com/?search=webtransport https://caniuse.com/?search=webtransport

eis 4y ago
The information there is indeed incorrect. I have updated my comment accordingly.

eis 4y ago

> Interesting, do you have a source? Or did you try it? https://caniuse.com/webtransport https://caniuse.com/webtransport > The article does seem to answer these questions. Not for me. There's no usecase mentioned that is not possible today unless you count using it from inside a worker as a usecase I guess. I wonder btw why they compare WebTransports datagrams to WebSockets reliable streams. The equivalent to WebSockets would be the reliable Streams API of WebTransport. The issue with Head Of Line blocking can be easily solved by opening multiple WebSocket connections. WebTransport just has that solved instead within the protocol.

markdog12 4y ago
> https://caniuse.com/webtransport https://caniuse.com/webtransport Yeah, it seems there's an older entry in there that's confusing. Not sure. > There's no usecase mentioned that is not possible today WebTransport does not really do anything that was previously impossible from an API standpoint, it improves on existing methods. > Head Of Line blocking can be easily solved by opening multiple WebSocket connections. WebTransport just has that solved instead within the protocol. Yes, and solving it within the protocol is simpler and more efficient. > It needs a bunch of examples Agreed, that would be nice.
- eis 4y ago
  > Yeah, it seems there's an older entry in there that's confusing. Not sure. I have just tried it on Chrome 103 on Android 12 and WebTransport worked. The information on caniuse.com is indeed incorrect. > WebTransport does not really do anything that was previously impossible from an API standpoint, it improves on existing methods. Yup, that's why I want to see it widely supported. Any simplification is good for the web. Though WebTransport unfortunately does not improve on every aspect of the existing APIs. It also has limitations that WebRTC does not have like P2P or easily piping media for using in MediaStreams.