w3c / webtransport

WebTransport is a web API for flexible data transport
https://w3c.github.io/webtransport/
Other
848 stars 50 forks source link

Add protocols constructor argument to WebTransport + protocol read arg #598

Closed jan-ivar closed 2 months ago

jan-ivar commented 7 months ago

Fixes #536. Right now this seems only defined for HTTP/3, so that's what I went with. Is this what we want?


Preview | Diff

jan-ivar commented 7 months ago

Meeting:

jan-ivar commented 7 months ago

Meeting:

jan-ivar commented 5 months ago

Meeting:

wilaw commented 5 months ago

Could we call this "applicationProtocol"? This avoids overloading the multiple references to internet protocols (UDP, QUIC, WebTransport) and instead refers to the protocol we wish to describe, which is defined completely by the application using the WebTransport connection.

jan-ivar commented 4 months ago

Meeting:

jan-ivar commented 4 months ago

IETF preferred "protocol" by overwhelming margin in a poll (19 protocol, 3 subprotocol, 9 applicationLevelProtocol)

wilaw commented 3 months ago

Note https://github.com/ietf-wg-webtrans/draft-ietf-webtrans-overview/issues/15#issuecomment-2299876480, calling for harmonization around the use of "protocol".

jan-ivar commented 2 months ago

The API is now "protocol" throughout, except prose still uses "subprotocol" to disambiguate it from its own § 3. Protocol concepts (HTTP3 does a similar thing).

jan-ivar commented 2 months ago

s/subprotocol/protocol/ for variable names