Fwd: Enabling QUIC in tip-of-tree

Skip to first unread message

Ryan Sleevi

Mar 9, 2020, 1:45:15 PM3/9/20
to Chromium Embedders, Dharani Govindan
Forwarding to embedder-dev@, although discussion is requested on net-dev@

---------- Forwarded message ---------
From: 'Dharani Govindan' via net-dev <net...@chromium.org>
Date: Mon, Mar 9, 2020 at 1:31 PM
Subject: Enabling QUIC in tip-of-tree
To: chromium-dev <chromi...@chromium.org>, <net...@chromium.org>, <blin...@chromium.org>

Hello Fellow Chrome Developers,


QUIC has been enabled in Google Chrome for 90% of users via a multi-year field trial, and default enabled in a number of popular mobile apps including Google Search and YouTube, for several years. As our various blog posts and SIGCOMM 2017 paper have detailed, this has been a huge win for performance and user experience and we are confident that our QUIC support is robust and solid.


As a result, we will be changing the way QUIC is enabled in M82. Instead of explicitly enabling QUIC when the network stack is configured, QUIC will be enabled by default. This means that QUIC will be implicitly enabled for embedders who accept the default options. An embedder will need to explicitly disable QUIC if they do not wish to support it. This can be done by setting the "enable_quic" member of URLRequestContextConfig to false.


If you have any questions please feel free to contact net...@chromium.org



You received this message because you are subscribed to the Google Groups "net-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to net-dev+u...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/net-dev/CAD9fJvzBO0tme3fjyjyW8qe7FST3B-%2BM%3DWyu-rFwWj3OQaV%3DAQ%40mail.gmail.com.
Reply all
Reply to author
0 new messages