W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2013

Multi-GET, extreme compression?

From: Phillip Hallam-Baker <hallam@gmail.com>
Date: Sat, 16 Feb 2013 13:01:59 -0500
Message-ID: <CAMm+LwiF6EM8_aQgUm=nPS5XqaG25iRGNke_rnHTM1vTGMXdfg@mail.gmail.com>
To: "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
HTTP 1.1 has a request/response pattern. This covers 90% of needs but means
that if the protocol is followed correctly forces a round trip delay on
each content request. Which of course leads to various browsers pushing the
envelope and pushing multiple requests out before responses have come back.

With content streams this is not necessary of course... In fact that is
pretty much the purpose of having streams.

Which suggests a need for a Multi-GET method to allow a request for a list
of content...

If we had such a method then the format would be something like

MGET <Common Headers> List <URI, Content header>

And the typical communication pattern of a browser would be:

GET /toplevel.html
MGET </image1.jpg /image2.jpg ...>

Given this particular communication pattern which has an implicit delta
encoding, do we really need to worry about a separate delta encoding?


-- 
Website: http://hallambaker.com/
Received on Saturday, 16 February 2013 18:02:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 16 February 2013 18:02:28 GMT