- From: Yutaka Hirano <notifications@github.com>
- Date: Thu, 18 Feb 2021 02:33:41 -0800
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 18 February 2021 10:33:53 UTC
> 1. Does this PR allow for a server to specify that it does not support pooling? That is, that the origin requuires that HTTP/3 Request/Response not be combined with WebTransport on the same connection or that WebTransport connections should not be pooled? We need to specify something in WEBTRANSPORT-HTTP3. I don't find the feature in the current protocol spec. The most natural way to express such intention is encoding the intention in the SETTINGS frame the server sends. If we choose the way, we'll be able to handle it in w3c/webtransport and we will not need to add logic in whatwg/fetch. > 2. Does this PR change the transport requirements for an HTTP/3 connection established for Request/Response (e.g. not for WebTransport)? For example, will an HTTP/3 connection to be established for Request/Response now require that the server support HTTP/3 datagrams? No. With this PR, the client (i.e., the user agent) expresses its support for WebTransport and datagrams via the SETTINGS frame. > 3. Does this PR allow HTTP/3 Request/Response to reuse a WebTransport connection? Yes. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/pull/1171#issuecomment-781247016
Received on Thursday, 18 February 2021 10:33:53 UTC