- From: James M Snell <jasnell@gmail.com>
- Date: Fri, 23 Aug 2013 14:58:55 -0700
- To: Martin Thomson <martin.thomson@gmail.com>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
Received on Friday, 23 August 2013 21:59:22 UTC
Integer is helpful for things like content-length. I'd rather keep that one. The only difference between it and timestamp is one bit so merging them wouldn't do much, but we could just dump timestamp and just say that timestamp headers use integer. But that makes translation to http/1 harder. You'd have to know in advance that any given header is a http-date or number. On Aug 23, 2013 2:53 PM, "Martin Thomson" <martin.thomson@gmail.com> wrote: > On 23 August 2013 14:48, James M Snell <jasnell@gmail.com> wrote: > > I went with this so we could reserve a few additional types but I'm not > that > > particular about it. Whichever works. > > Extensibility is overrated. You only need a few points of articulation. > > I wonder if you could possibly drop Integer from the list (or even > merge it with Timestamp). >
Received on Friday, 23 August 2013 21:59:22 UTC