W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2012

Re: Re[2]: FYI... Binary Optimized Header Encoding for SPDY

From: Poul-Henning Kamp <phk@phk.freebsd.dk>
Date: Thu, 02 Aug 2012 12:28:54 +0000
To: "Adrien de Croy" <adrien@qbik.com>
cc: "Yoav Nir" <ynir@checkpoint.com>, "Mike Belshe" <mike@belshe.com>, "James M Snell" <jasnell@gmail.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Message-ID: <1457.1343910534@critter.freebsd.dk>
In message <em57fc159f-7eb0-4506-89a6-a55d04ed64ed@reboist>, "Adrien de Croy" w
rites:

>In the end though, when I get a file attributes from windows, the 
>filetime members are in 64 bit ns since epoch.  So either I'd convert 
>to something before transmission, or push that task through to the 
>client side.

Just because somebody else did it wrong, doesn't mean we should
emulate them.

>I don't know what sort of timestamps unix serves up.  I'd expect it 
>mainly to be determined by underlying clock hardware on motherboards.  

No, it's been standardized (wrong!) for 20+ years: struct timeval
and struct timespec, both of which are also mixed-radix formats.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.
Received on Thursday, 2 August 2012 12:29:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 2 August 2012 12:29:32 GMT