- From: Yves Lafon <ylafon@w3.org>
- Date: Thu, 25 Jul 2013 08:21:46 -0400 (EDT)
- To: Noah Mendelsohn <nrm@arcanedomain.com>
- cc: "Appelquist Daniel (UK)" <Daniel.Appelquist@telefonica.com>, "www-tag@w3.org" <www-tag@w3.org>
On Tue, 23 Jul 2013, Noah Mendelsohn wrote:
>
> On 7/22/2013 11:16 AM, Yves Lafon wrote:
>> The crux of HTTP/2.0 is that its goal is to be compatible with HTTP/1.1 as
>> much as possible, meaning that from AWWW there should be no changes in the
>> use of HTTP.
>
> I think you mean: AWWW as published doesn't explictly deal with issues at the
> level where HTTP 2.0 proposes to change things. That's mostly true.
Yes, mostly, there is one thing that is not covered, it's section 8.2 of
the http2 spec: "8.2. Server Push" [1]
> Nonetheless, these turn out to be levels where the community is now working
> hard to improve or fix the architecture. It's not 100% clear that a revision
> to AWWW shouldn't explore some of the issues and principles that arise in the
> HTTP 2.0 discussions.
The document should definitely be reviewed, at least to check that the
overall semantic didn't change.
[1] https://tools.ietf.org/html/draft-ietf-httpbis-http2-04#section-8.2
--
Baroula que barouleras, au tiéu toujou t'entourneras.
~~Yves
Received on Thursday, 25 July 2013 12:21:49 UTC