- From: Bjoern Hoehrmann <derhoermi@gmx.net>
- Date: Fri, 15 Nov 2013 14:27:31 +0100
- To: "Roy T. Fielding" <fielding@gbiv.com>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
* Roy T. Fielding wrote: >1.2.1. Delta Seconds > > The delta-seconds rule specifies a non-negative integer, representing > time in seconds. > > delta-seconds = 1*DIGIT > > A recipient parsing a delta-seconds value and converting it to binary > form ought to use an arithmetic type of at least 31 bits of non- > negative integer range. If a cache receives a delta-seconds value > greater than the greatest integer it can represent, or if any of its > subsequent calculations overflows, the cache MUST consider the value > to be either 2147483648 (2^31) or the greatest positive integer it can > conveniently represent. > > Note: The value 2147483648 is here for historical reasons, > effectively represents infinity (over 68 years), and does not need > to be stored in binary form; an implementation could produce it as > a canned string if any overflow occurs, even if the calculations > are performed with an arithmetic type incapable of directly > representing that number. What matters here is that an overflow > be detected and not treated as a negative value in later > calculations. > >Cool? I http://lists.w3.org/Archives/Public/ietf-http-wg/2013JanMar/1270.html raised this issue back in March and the text above is fine with me. -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
Received on Friday, 15 November 2013 13:27:55 UTC