W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2010

Re: short-time client side caching and clock skew

From: Mark Nottingham <mnot@mnot.net>
Date: Tue, 1 Jun 2010 21:57:10 +1000
Cc: 'Henrik Nordström' <henrik@henriknordstrom.net>, <ietf-http-wg@w3.org>
Message-Id: <C7F9B70D-7EE3-4AC7-99D2-03A787C3D1D6@mnot.net>
To: Jorrit Jongma <Jorrit@Jongma.org>
See also:
  http://www.w3.org/mid/0BD82EFC-9F0D-4122-89FE-E245E32AE22C@yahoo-inc.com

If you're going to suggest replacement text, please incorporate the changes in -latest (if you haven't already); see 
  http://trac.tools.ietf.org/wg/httpbis/trac/ticket/29

Cheers,


On 31/05/2010, at 11:04 PM, Jorrit Jongma wrote:

> Henrik,
> 
> Thank you for your insights and corrections.
> 
> If I understand you correctly, the following pseudo-code would cover all the cases, taking -09 as base, and completely bypassing date_value if possible:
> 
> if (response_version_1_1 && !response_via_1_0) {
> 	corrected_initial_age = age_value + (response_time - request_time);
> } else {
> 	apparent_age = max(0, response_time - date_value);
> 	corrected_received_age = max(apparent_age, age_value);
> 	response_delay = response_time - request_time;
> 	corrected_initial_age = corrected_received_age + response_delay;
> }
> resident_time = now - response_time;
> current_age = correct_initial_age + resident_time;
> 
> I have tested current operation in a few browsers, and the results are not encouraging; if the above is judged correct it is my intent to submit bug tickets to some of these browser manufacturers and see if they will update.
> 
> Regards,
> Jorrit
> 
> 
> 


--
Mark Nottingham     http://www.mnot.net/
Received on Tuesday, 1 June 2010 11:57:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:19 GMT