Re: CONTINUATION proposal w/ minimum change

In message <>, Jason Greene writes:

>> As I stated earlier, this proposal adds more complexities than it
>> removes and it serves just for treating 0.02%.

Given the amount of complexity huge HTTP headers and the proposed
handing with CONTINUATION frames cause, I think it is time the WG
puts the horse in front of the cart:

Remove CONTINUATION from the draft.

Declare that the compressed headers can be no longer than 16383 bytes
in "vanilla" HTTP/2.

Applications needing longer headers can either remain in HTTP/1
(where it presumably already works for them), they can redesign
their application to use smaller headers or they can push a negotiable
HTTP/2.0 extension for sending bigger requests through the IETF.

Loosing 0.02% of the potential HTTP/2 traffic to that decision
is utterly trivial compared to the amount of traffic lost to
browers which will not support HTTP/1 upgrade.

Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.

Received on Tuesday, 1 July 2014 19:55:06 UTC