- From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
- Date: Wed, 30 Aug 2017 08:16:02 +0000
- To: public-webscreens@w3.org
Great draft! You may complete the rest of the message definitions. How confident we are at this point after completing the evaluation of QUIC #9 and RTCDataChannel #10 (aka Mozilla's proposal) that these two transports are the ones this control protocol is to be layered on top off, and not others? I've understood for both of these transports, there's implementers' interest, which is a good sign. Is anyone thinking of using HTTP/2, WebSockets, or a custom protocol anymore? The sooner we're able to nail down the set of transports to target, the easier it will be to make progress on the control protocol. So I'm wondering if we could nail down the supported transports now to ensure the constraints in protocol design would be known upfront. -- GitHub Notification of comment by anssiko Please view or discuss this issue at https://github.com/webscreens/openscreenprotocol/pull/44#issuecomment-325917624 using your GitHub account
Received on Wednesday, 30 August 2017 08:15:59 UTC