Re: New Version Notification for draft-kerwin-http2-encoded-data-01.txt

[Greg Wilkins <[e-mail]>]

Matthew,

why are the compression contexts frame only?    Doesn't that make this
extension very vulnerable to fragmentation, specially if we drop
END_SEGMENT as we have done.

Surely there is no harm in having a compression context that is per stream?

If there is a desire to have per frame contexts, can't that be done with
different types rather than saying that no type can have a stream context?

Note that I would like to see transport layer compression because it is
currently a nightmare to implement application layer compression - getting
all the etag, vary headers right is more complex than you'd think,
specially when mixed in with some silly aspects of the servlet API (write
this.... no opps don't)  plus most containers struggle with
applications/content-types that set content-encoding themselves.

cheers



On 22 July 2014 10:00, Matthew Kerwin <[e-mail]> wrote:

> For those interested in such things:
>
> ---------- Forwarded message ----------
> From: <[e-mail]>
> Date: 22 July 2014 09:46
>
>
>
> A new version of I-D, draft-kerwin-http2-encoded-data-01.txt
> has been successfully submitted by Matthew Kerwin and posted to the
> IETF repository.
>
> Name:           draft-kerwin-http2-encoded-data
> Revision:       01
> Title:          HTTP/2 Encoded Data
> Document date:  2014-07-22
> Group:          Individual Submission
> Pages:          9
> URL:
> http://www.ietf.org/internet-drafts/draft-kerwin-http2-encoded-data-01.txt
> Status:
> https://datatracker.ietf.org/doc/draft-kerwin-http2-encoded-data/
> Htmlized:
> http://tools.ietf.org/html/draft-kerwin-http2-encoded-data-01
> Diff:
> http://www.ietf.org/rfcdiff?url2=draft-kerwin-http2-encoded-data-01
>
> Abstract:
>    This document introduces new frame types for transporting encoded
>    data in HTTP/2, and an associated error code.
>
>
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
>
>
>
> --
>   Matthew Kerwin
>   http://matthew.kerwin.net.au/
>



-- 
Greg Wilkins <[e-mail]>
http://eclipse.org/jetty HTTP, SPDY, Websocket server and client that scales
http://www.webtide.com  advice and support for jetty and cometd.