- From: Mark Nottingham <notifications@github.com>
- Date: Sun, 18 Nov 2018 14:03:07 -0800
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Sunday, 18 November 2018 22:03:28 UTC
@arturjanc Likewise, I'm not dead-set on splitting them out; just trying to illustrate that the binary approach isn't actually giving us what we might think. I agree it's likely to be top-heavy; isn't everything on the Web a Ziph curve, after all? WRT developer ergonomics - I don't know that accessing several single header values is more onerous than parsing one complex one -- especially if both approaches use structured headers -- but of course YMMV. >From a compression efficiency perspective, the effect I illustrate will become more pronounced when you add more fields; it'd be interesting to see what Chrome's numbers are once you add `mode`. And of course if there are more fields that might be added later, that changes things too. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/280#issuecomment-439729825
Received on Sunday, 18 November 2018 22:03:28 UTC