Contact emailsh...@chromium.org, pmee...@chromium.org,
yoavwe...@chromium.org, kenjibah...@chromium.org

Explainerhttps://github.com/yoavweiss/compression-dictionary-transport

Specification

Summary

This feature adds support for using designated previous responses, as an
external dictionary for Brotli-compressing HTTP responses.


Blink componentBlink>Network
<https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ENetwork>

Motivation

If the browser and server share a dictionary, using the dictionary for
compression can significantly reduce the amount of data transferred. This
is especially useful for incremental library updates, or when browsing
multiple pages that have a lot of common parts in their files.


Initial public proposalhttps://github.com/WICG/proposals/issues/90

TAG review

TAG review statusPending

Risks


Interoperability and Compatibility



*Gecko*: No signal

*WebKit*: No signal

*Web developers*: No signals

*Other signals*:

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that
it has potentially high risk for Android WebView-based applications?



Debuggability



Is this feature fully tested by web-platform-tests
<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>
?Not yet, but tests will be written as part of the implementation.

Flag nameTBD

Requires code in //chrome?False

Tracking bughttps://crbug.com/1413922

Estimated milestones

No milestones specified


Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5124977788977152

This intent message was generated by Chrome Platform Status
<https://chromestatus.com/>.

-- 
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+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CADk0S-Vb1ON2XT2%2BBP27tJ4ivjgyu63jcd667am4TwcVFGsbuw%40mail.gmail.com.

Reply via email to