3 ms·
For example, HTTP/3 uses QPACK, which has a static predefined list of HTTP header strings included in the standard. What strings you ask? The top hits Google
by jiggawatts 3y ago
For example, HTTP/3 uses QPACK, which has a static predefined list of HTTP header strings included in the standard.
What strings you ask?
The top hits Google captured from their data centre egress.
E.g.: https://www.ietf.org/archive/id/draft-ietf-quic-qpack-20.html#static-table https://www.ietf.org/archive/id/draft-ietf-quic-qpack-20.htm...
Notice that "content-encoding" includes br (Brotli), a Google compression algorithm that essentially only they were using at the time.
- tgma 3y agoI don't understand what the objection is to the methodology. Are you claiming there is another party that has a better sample (even subjectively so) and was pushing it and didn't succeed? If anything, standards committees are often overly annoying and biased the other way just because some other company representative wants to justify their presence. That is also cherry picked. For example standardizing ALPN over NPN which is largely a downgrade for the average user done in the standard process. The examples you use simply indicate a certain company is ahead of the game in solving problems others also have.