- From: Anne van Kesteren via GitHub <sysbot+gh@w3.org>
- Date: Mon, 07 Dec 2020 09:13:23 +0000
- To: public-webrtc@w3.org
annevk has just created a new issue for https://github.com/w3c/webrtc-pc: == Share some connection infrastructure with Fetch == I think there are basically two reasons why we would want centralized connection management in the platform: * Consistent handling of overrides of resolving names (domains), e.g., mapping localhost to the loopback address, as discussed at https://github.com/whatwg/fetch/issues/1118. * Consistent requirements on partitioning of all aspects of the connection. https://fetch.spec.whatwg.org/#network-partition-keys in Fetch is now used for connections and the HTTP cache, but it should also apply to the DNS cache, etc. Having those kind of requirements once would be beneficial. Also in case we ever decide to adjust them. (See also https://github.com/w3c/webtransport/issues/128.) Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2613 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 7 December 2020 09:13:25 UTC