- From: Timothy Knox <tdk@thelbane.com>
- Date: Thu, 2 Aug 2012 12:29:47 -0700
- To: ietf-http-wg@w3.org
Somewhere on Shadow Earth, at Thu, Aug 02, 2012 at 10:48:52AM -0700, James M Snell wrote: <snip> > This is precisely why I favor the introduction of a binary value option and > the definition of highly-optimized binary encodings for the most commonly > used protocol headers (like method, version, etc). Things like Host and > Request URI need to be looked at tho. I suspect that, for a variety of > reason, we'll want to keep limiting those values to ASCII only. (just > because the value COULD be UTF-8, doesn't mean a specific header definition > cannot limit the actual value to some reasonable subset). For the Host header, I have just three letters to say to you: I-D-N. :-) -- Timothy Knox <mailto:tdk@thelbane.com> I like to say that in the old days, if you reinvented the wheel, you would get your wrist slapped for not reading. But nowadays people are reinventing the flat tire. I'd personally be happy if they reinvented the wheel, because at least we'd be moving forward. -- Alan Kay
Received on Thursday, 2 August 2012 19:30:11 UTC