Re: [hybi] hum #3: Message

Dave Cridland <dave@cridland.net> Fri, 06 August 2010 20:26 UTC

Return-Path: <dave@cridland.net>
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 3D5233A68DB for <hybi@core3.amsl.com>; Fri, 6 Aug 2010 13:26:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.491
X-Spam-Level:
X-Spam-Status: No, score=-2.491 tagged_above=-999 required=5 tests=[AWL=0.108, 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 1fNFpX3iI8yx for <hybi@core3.amsl.com>; Fri, 6 Aug 2010 13:26:20 -0700 (PDT)
Received: from peirce.dave.cridland.net (peirce.dave.cridland.net [217.155.137.61]) by core3.amsl.com (Postfix) with ESMTP id 13DF13A68D9 for <hybi@ietf.org>; Fri, 6 Aug 2010 13:26:20 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by peirce.dave.cridland.net (Postfix) with ESMTP id 57809116809F; Fri, 6 Aug 2010 21:26:51 +0100 (BST)
X-Virus-Scanned: Debian amavisd-new at peirce.dave.cridland.net
Received: from peirce.dave.cridland.net ([127.0.0.1]) by localhost (localhost.localdomain [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id toq3yXT2w+5I; Fri, 6 Aug 2010 21:26:50 +0100 (BST)
Received: from puncture (puncture [217.155.137.60]) by peirce.dave.cridland.net (Postfix) with ESMTPA id EE897116809E; Fri, 6 Aug 2010 21:26:49 +0100 (BST)
References: <4C5AE93D.4040803@ericsson.com> <Pine.LNX.4.64.1008051758290.5947@ps20323.dreamhostps.com> <AANLkTik0kbh14s2JZARY2MFh0iNGV7H+B4Px4yG+wX44@mail.gmail.com> <71BCE4BF-D3F6-4F94-BE76-306BDF6A2E67@apple.com> <Pine.LNX.4.64.1008051930160.5947@ps20323.dreamhostps.com> <4C5B1695.6070704@gmx.de> <F8E2F702-9F74-4316-B3B2-D5A731409ABF@apple.com> <AANLkTin=gO9D8K5NVhqCRKki-jrDmTYqF-gBjp9X41GN@mail.gmail.com> <4C5BF15E.1090608@noemax.com> <AANLkTinXLPmBACd3ji0V9wkAWmxOR7qBMED19KKMvJrd@mail.gmail.com> <AANLkTi=RWdqDDgy24C6qtUSr+5R5p=P15B=+aUZuE16Q@mail.gmail.com> <4C5C07D6.1030208@noemax.com> <AANLkTimj9RvzL8E+FmH=vT_TeECVNmDPXY0ymPnvBHSZ@mail.gmail.com> <4C5C31DF.3030608@caucho.com>
In-Reply-To: <4C5C31DF.3030608@caucho.com>
MIME-Version: 1.0
Message-Id: <2286.1281126409.976140@puncture>
Date: Fri, 06 Aug 2010 21:26:49 +0100
From: Dave Cridland <dave@cridland.net>
To: Scott Ferguson <ferg@caucho.com>, Server-Initiated HTTP <hybi@ietf.org>, John Tamplin <jat@google.com>
Content-Type: text/plain; delsp="yes"; charset="us-ascii"; format="flowed"
Subject: Re: [hybi] hum #3: Message
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: Fri, 06 Aug 2010 20:26:21 -0000

On Fri Aug  6 17:01:35 2010, Scott Ferguson wrote:
> As a practical matter, a 16-bit short length would be better  
> because buffer sizes are typically in the 1k to 64k range, and a  
> 16-bit length lets the implementation pre-allocate the frame header  
> for any message/chunk.
> 
> 
I'm happier with the "short" being 255 octets, because the only case  
we really need to minimize overhead is in mobile cases, where the  
power levels possible by transferring packets <128 octets are  
substantial and important.

I'm not wed to this, mind.

A good argument in favour is that it could be expected that more  
messages would be on both sides of the division with a 16-bit short  
length width. I'm not sure the predicate is true though.


> With an 8-bit length, the implementation either needs to shift  
> bytes in the buffer when the message is 255 bytes long or it needs  
> to preallocate the long frame header.

Indeed. I'm told, however, that this is not such a big deal. FWIW,  
unaliagned access to wrong-endian data is something I have experience  
of, and as far as I can tell, is not a substantial overhead.

Dave.
-- 
Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade