Re: The use of binary data in any part of HTTP 2.0 is not good

Ya, that still sounds bad :)
(Too bad self-modifying code is the hallmark of a virus these days...)
-=R


On Tue, Jan 22, 2013 at 2:27 AM, Amos Jeffries <squid3@treenet.co.nz> wrote:

> On 22/01/2013 10:33 p.m., Adrien W. de Croy wrote:
>
>>
>>
>> ------ Original Message ------
>> From: "Nico Williams" <nico@cryptonector.com>
>>
>>>
>>> We could also go with receiver-makes right. In this case every
>>> message (request, response) must include a BOM and then the receiver
>>> makes right. This strikes me as fair, if not, perhaps, compelling..
>>>
>> I'd rather have a milllion htons and ntohs than having to procede each
>> one with an if statement as well.
>>
>> so I think this is a bad idea
>>
>>
> You could optimize by writing two parsers in complete duplicate and
> switching between them on sighting the BOM.
> It only doubles the memory footprint instead of the CPU footprint. ;-)
>
> Amos
>
>