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

Re: bohe and delta experimentation...

From: Adrien W. de Croy <adrien@qbik.com>
Date: Sat, 19 Jan 2013 01:00:31 +0000
To: "Phillip Hallam-Baker" <hallam@gmail.com>, "James M Snell" <jasnell@gmail.com>
Cc: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Message-Id: <emd6c32c19-6374-45d5-a940-181a329b2604@bombed>


------ Original Message ------
From: "Phillip Hallam-Baker" <hallam@gmail.com>
>
>
>On Wed, Jan 16, 2013 at 5:07 PM, James M Snell <jasnell@gmail.com> 
>wrote:
>>After going a number of scenarios with bohe using a variety of 
>>stream-compression scenarios it's painfully obvious that there is 
>>really no way around the CRIME issue when using stream-compression. So 
>>with that, I'm turning my attention to the use of Roberto's delta 
>>encoding and exploring whether or not binary optimized values can make 
>>a significant difference (as opposed to simply dropping in 
>>huffman-encoded text everywhere).
>>
>>I'm starting with dates first...
>>
>>Right now, dates in http/1 requests are rather inefficient. The 
>>existing date-time format wastes a significant amount of space, albeit 
>>across only a relatively few headers. On the plus side, these tend to 
>>compress well, but given that the dates change frequently 
>>request-to-request, they will be short-lived in the delta context.
>
>Why do HTTP request messages have dates in them anyhow?

Date is used in caching, with Last-Modified it is used to calculate age 
of resource when served for purposes of estimating max-age for heuristic 
caching.

This presumes the same clock was used to generate Date as Last-Modified.

So I don't think we can lose it.

Adrien
Received on Saturday, 19 January 2013 01:01:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 19 January 2013 01:01:27 GMT