Re: [w3ctag/design-reviews] WebTransport (#389)

Responses to dbaron's comments from 10 days ago:


RTCQuicTransport is the p2p impl of a WebTransport.  I made https://github.com/WICG/web-transport/issues/41 to track making that more clear.

The explainer has now been updated to use WHATWG streams.  We plan to update the spec to use them as well after some more discussion on how WHATWG streams should work (in particular for creating send streams and bidirectional streams).

We definitely want WebTransports to work in WebWorkers, we simply didn't think to say that explicitly.  

The W3C spec references the IETF specs.  Victor made https://github.com/WICG/web-transport/issues/37 to track that.

I can't find any example of "!!". Perhaps that went away when we moved to WHATWG streams in the explainer.

On the nullability of receiveDatagrams(): you're right, that's a mistake.  But we decided on a different approach that doesn't return null (see https://github.com/w3c/webrtc-quic/issues/124).  We just need a PR for it.

On the goofiness of receiveDatagrams() only being called once at a time: that will probably go away with 
the switch to WHATWG streams.  


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/389#issuecomment-511017984