Re: [hybi] Framing take IV

Scott Ferguson <ferg@caucho.com> Wed, 04 August 2010 01:34 UTC

Return-Path: <ferg@caucho.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 828CA3A68AB for <hybi@core3.amsl.com>; Tue, 3 Aug 2010 18:34:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2GHQnoC4G7ea for <hybi@core3.amsl.com>; Tue, 3 Aug 2010 18:33:03 -0700 (PDT)
Received: from smtp113.biz.mail.re2.yahoo.com (smtp113.biz.mail.re2.yahoo.com [66.196.116.98]) by core3.amsl.com (Postfix) with SMTP id 4C2FF3A699A for <hybi@ietf.org>; Tue, 3 Aug 2010 18:31:59 -0700 (PDT)
Received: (qmail 46331 invoked from network); 4 Aug 2010 01:31:40 -0000
Received: from [192.168.1.11] (ferg@66.92.8.203 with plain) by smtp113.biz.mail.re2.yahoo.com with SMTP; 03 Aug 2010 18:31:40 -0700 PDT
X-Yahoo-SMTP: L1_TBRiswBB5.MuzAo8Yf89wczFo0A2C
X-YMail-OSG: HGtkhgMVM1kjWJaSKnKokGAnsTmWW2FVtFkE.KqkCfuQX.x .p21g2CRr.y5sIXQZRYSYyg5E5hbXmfU3bTOf6xsqbhVEyPVWICQKNCA4pi_ Ub0wePIGd0G4XxSgrkYiqPdf8kB4wD0dD04mTEv5PFovH0u0qzNtZJ_MLydT N9IA7WX9tcLMGpw0Yv9J6Xux8zw4JTRVyv7EDhS3AfqeyaHbvfezpMwD1.q3 0s33LOGMHWfVG4VITHIu6AsEhin8Tjb54Yv7HS_jtHTB_cF96a8byTqXrKQQ _.sDG.l9swvTgTuTYWfzJxmoC8Xo4bydd41rsrdwrzUulBZW_yjuFCuOh_8k hSs40lTJr.ELYlBjNUxMxIi93JmbnDqqVAdvTrssAtptK6hdIwouHBGwArq_ 6S5ZmJbGcVZn7jFSw0Q--
X-Yahoo-Newman-Property: ymail-3
Message-ID: <4C58C2F6.8050608@caucho.com>
Date: Tue, 03 Aug 2010 18:31:34 -0700
From: Scott Ferguson <ferg@caucho.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: Maciej Stachowiak <mjs@apple.com>
References: <AANLkTinyrDoG5d_Ur6HVRy=SgMPjLzJtpJ++Ye=1DQdj@mail.gmail.com> <Pine.LNX.4.64.1008040050040.5947@ps20323.dreamhostps.com> <28A6543A-5CA6-42B7-8D2E-F5511EE20008@apple.com>
In-Reply-To: <28A6543A-5CA6-42B7-8D2E-F5511EE20008@apple.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: hybi@ietf.org
Subject: Re: [hybi] Framing take IV
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Aug 2010 01:34:11 -0000
X-List-Received-Date: Wed, 04 Aug 2010 01:34:11 -0000

Maciej Stachowiak wrote:
> On Aug 3, 2010, at 5:53 PM, Ian Hickson wrote:
>
>   
>> On Wed, 4 Aug 2010, Greg Wilkins wrote:
>>     
>>> I think that we have reasonable consensus on something like:
>>>
>>>  +--------------------------------------------------+
>>>  | frag(1) |unused(3) | opcode(4) |  Length(16)     |
>>>  +--------------------------------------------------+
>>>  |                      Data                        |
>>>  +--------------------------------------------------+
>>>       
>> Why would we have a fixed length field with fragmentation rather than a 
>> variable length field?
>>
>> If we can have a variable width length field, do we need to support 
>> fragmentation in the first version? I could see an argument for supporting 
>> fragmentation in the case of multiplexing, but without that it doesn't 
>> seem to actually gain us anything.
>>     
>
> I agree. I can't see any benefit to fragmentation over a variable-size length field for an initial version without multiplexing. If the variable-size length field is well-designed, then in the common case where the message size is small it will only cost one extra branch to read the length. In the rare case where the message size is large, a variable-size length is easier to deal with than reassembling fragments, and easier on the sending side too.
>   

Some of us don't have infinite memory when sending messages.

-- Scott