My $0.02

Define "Header Block" as the set of headers at the HTTP level, i.e. the set
of headers before the data in a response, the set of trailers after the
data in a response, the pushed set of headers that identify the pushed
resource, etc.

In the mapping layer map these "Header Block"s to frame
types,  PUSH_PROMISE frames for the identification of pushed resource,
HEADERS frames for response headers, trailers, etc.

In the framing layer define the encoding/compression of the "Headers
Block"s into a sequence of those frames types that must be contiguous and
end with the END_HEADERS flag set.



On Fri, Jun 28, 2013 at 9:49 PM, James M Snell <notifications@github.com>wrote:

> In draft-ietf-httpbis-http2.xml:
>
> > +        </t>
> > +        <t>
> > +          If the total size of a compressed header block exceeds the expected
> > +          maximum size allowed for an individual HEADERS or PUSH_PROMISE frame,
> > +          the octets of the compressed header block are split among multiple
> > +          individual frames that MUST be transmitted, in order, without any
> > +          other interleaved frames. The frame carrying the final portion of
> > +          the compressed header block MUST include a flag indicating that the
> > +          header block is complete.
> > +        </t>
> > +        <t>
> > +          Whenever this specification mentions sending a header block,
> > +          the meaning is that one or more HEADERS frames containing the
> > +          compressed content of a single header block is to be sent.
> > +          Whenever sending a "push promise" is mentioned, the meaning
> > +          is that one or more PUSH_PROMISE frames are being sent.
>
> I changed from "sets of headers" to attempt to achieve some kind of
> consistency in the wording. Some places used "header block", other places
> used "sets of headers", other places talked about sequences of HEADERS
> frames, etc. We need to come up with clear language that states that a
> "Header block" is a logical set that can span either a sequence of
> PUSH_PROMISE frames or a sequence of HEADERS frames... wait... maybe that's
> the exact language we need ;-)
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/http2/http2-spec/pull/151/files#r4951377>
> .
>