- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Wed, 5 Dec 2018 04:12:18 +1100
- To: Mike West <mkwst@google.com>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
On Fri, Nov 30, 2018 at 7:38 PM Mike West <mkwst@google.com> wrote: > That seems pretty reasonable to me, though I'm not sure how much space we have to work with in the static table. Chrome's current user agent string comes in at around ~150 characters, depending on platform. Taking that as a baseline, how many strings could we reasonably encode? Can the table expand to an extend that would allow it to cover enough of the UA market? The cost is in static code size only, so in theory it could be modestly large. (Those concerned with static code size can replace the strings with symbols representing the semantics without preserving the syntax - those 150+ characters could be just be a static IS_CHROME)
Received on Tuesday, 4 December 2018 17:12:53 UTC