Re: Make HTTP 2.0 message/transport format agnostic

  
p.s.
  
I wasn't for a second suggesting we should actually _use_ ASN.1 or any 
of its encodings.
  
It's just the only other system I know of which uses an abstract 
notation, and has numerous transfer encodings, so I wondered if any 
people knew whether that turned out to just be a waste of time because 
everyone just ended up using one of them.

------ Original Message ------
From: "Adrien W. de Croy" <adrien@qbik.com>
To: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
Cc: "Mark Nottingham" <mnot@mnot.net>;"Kevin Cathcart" 
<kevincathcart@gmail.com>;"ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Sent: 1/04/2012 11:36:45 a.m.
Subject: Re: Make HTTP 2.0 message/transport format agnostic
>
>------ Original Message ------ 
>From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> 
>>In message <em8582f3b4-bdc2-4f0b-ad2f-0dccfd9729fb@boist>, "Adrien W. 
>>de Croy" 
>>writes: 
>>
>>
>>>>>
>>>>>We should be able to learn from experience here... ASN.1 encoding 
>>>>>rules... have any become dominant? 
>>>>>
>>>>
>>>>
>>>>Have any ever broken the 1Gbit/s barrier ? 
>>>>
>>>>
>>>
>>>no idea. What I meant was dominant amongst themselves... e.g. one 
>>>preferred encoding (like DER) rather than the other 6 or 7. 
>>>
>>
>>
>>I don't care how dominant, if it doesn't do at least 40Gbit/sec with 
>>less than 10% of a contemporary machine, it's not relevant. 
>>
>
>that's not the point. 
>
>I'm trying to see if there is any knowledge out there about whether 
>there is any benefit to having multiple encodings or not, whether 
>experience has shown that it was a pointless exercise or not. 
>
>So throughput is meaningless. 
>
>
>>
>>
>>-- 
>>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 Saturday, 31 March 2012 23:53:30 UTC