Implement support for WebSockets over HTTP/3 in Chromium according to specification RFC9220 https://www.rfc-editor.org/rfc/rfc9220.html . This would only be used for secure WebSockets requests, and only if there is already an HTTP/3 connection where the server has already advertised support for WebSockets over HTTP/3 via the HTTP/3 SETTINGS parameter defined in the specification
Speed is the major motivation for this change. The number of connections to web servers over HTTP/3 is significantly increasing, but without WebSockets being supported over HTTP/3, it currently takes a few RTTs to negotiate a new connection. Supporting WebSockets over HTTP/3 would significantly cut down on latency. It also reduces the resource usage of the server implementing WebSockets, and so encourages adoption of WebSockets to the ecosystem.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
No milestones specified
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAN24jUFvbWH2pnX8me_3rgUV7XG7ZjnwTScytnB0B587q7Zo_g%40mail.gmail.com.