- From: Jeff Pinner <jpinner@twitter.com>
- Date: Tue, 30 Sep 2014 08:51:51 -0700
- To: Greg Wilkins <gregw@intalio.com>
- Cc: RUELLAN Herve <Herve.Ruellan@crf.canon.fr>, Willy Tarreau <w@1wt.eu>, Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
> At least one benefit is that you have the ability to pre compute values for > statics fields, or even series of static fields, so they do not need to be > calculated on every generation. > Now that we don't copy static entries to the dynamic field this generate > once use many times extends to fields using a static name and custom value. At most 4 headers can be used directly from the static table on a single message (:method, :path, :scheme, and accept-encoding) since none of the others have values, and that assumes the default values. For any other headers (or these without default values), assuming they are repeated between messages (likely given you are precomputing their values as static fields), they will be inserted into the dynamic table and their offsets will change as more headers are added. Thus I don't see how you can realistically reuse them with a precomputed offset, regardless of the location of the static table.
Received on Tuesday, 30 September 2014 15:52:18 UTC