- From: Jason Greene <jason.greene@redhat.com>
- Date: Thu, 4 Sep 2014 10:43:24 -0500
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: Amos Jeffries <squid3@treenet.co.nz>, ietf-http-wg@w3.org
On Sep 4, 2014, at 10:03 AM, Julian Reschke <julian.reschke@gmx.de> wrote: > On 2014-09-04 16:40, Amos Jeffries wrote: >> ... >> ... >>> Regardless, what are you trying to accomplish with binary header >>> values? >>> >> >> Good question. In a nutshell, the gain is simplicity for >> implementations no longer having to include base-64 encoder/decoders >> or spend CPU cycles doing the coding. >> ... > > I think the question is: why do you need binary data in header field values in the first place? Security tokens, cryptographic signatures, complex encoded types (e.g. ASN.1), specialty compressed values, precise serialization of IEEE754 floating point values, middleware intermediary tracking/routing information, unix timestamps etc -- Jason T. Greene WildFly Lead / JBoss EAP Platform Architect JBoss, a division of Red Hat
Received on Thursday, 4 September 2014 15:47:31 UTC