Re: [hybi] frame length encoding

Daniel Stenberg <daniel@haxx.se> Sat, 21 August 2010 19:29 UTC

Return-Path: <daniel@haxx.se>
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 C30F43A6847 for <hybi@core3.amsl.com>; Sat, 21 Aug 2010 12:29:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.431
X-Spam-Level:
X-Spam-Status: No, score=-3.431 tagged_above=-999 required=5 tests=[AWL=-1.182, BAYES_00=-2.599, HELO_EQ_SE=0.35]
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 KEVgLNumrRD5 for <hybi@core3.amsl.com>; Sat, 21 Aug 2010 12:29:48 -0700 (PDT)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by core3.amsl.com (Postfix) with ESMTP id 61FDF3A6801 for <hybi@ietf.org>; Sat, 21 Aug 2010 12:29:48 -0700 (PDT)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by giant.haxx.se (8.14.3/8.14.3/Debian-9.1) with ESMTP id o7LJUJOi003595; Sat, 21 Aug 2010 21:30:19 +0200
Date: Sat, 21 Aug 2010 21:30:19 +0200
From: Daniel Stenberg <daniel@haxx.se>
X-X-Sender: dast@giant.haxx.se
To: gustav <gustav.trede@gmail.com>
In-Reply-To: <AANLkTinrsT+wV48nHvVW_1ChGYffkq7jisU2-PZnMyKg@mail.gmail.com>
Message-ID: <alpine.DEB.2.00.1008212123460.27211@tvnag.unkk.fr>
References: <AANLkTimKbmcpgx8k0uXUWvCO=8w9pPrtV=3y4qh6363k@mail.gmail.com> <alpine.DEB.2.00.1008212037190.27211@tvnag.unkk.fr> <AANLkTinrsT+wV48nHvVW_1ChGYffkq7jisU2-PZnMyKg@mail.gmail.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
X-fromdanielhimself: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Greylist: Default is to whitelist mail, not delayed by milter-greylist-4.3.5 (giant.haxx.se [80.67.6.50]); Sat, 21 Aug 2010 21:30:19 +0200 (CEST)
Cc: Hybi <hybi@ietf.org>
Subject: Re: [hybi] frame length encoding
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: Sat, 21 Aug 2010 19:29:49 -0000

On Sat, 21 Aug 2010, gustav wrote:

>> I think I would prefer a plain 32 bit size, with no special treatment for
>> smaller fragments.

> Do you care to elaborate why ?.

I think most of the arguments around the sizes already have been mentioned and 
I'm not sitting on any new secrets.

I think sizes larger than 32bit will be very rare for Websockets, even for a 
long time to come into the future. Thus a vast vast majority of all frames 
will be sent with at least 4 bytes set to zero (with a fair amount of them not 
even implementing >32 bit support). In my mind, I think the few users that 
acually want to send more than 32bits of data can send it in multiple packets 
to get around the limitation. It's not like having a 32bit limit here will 
prevent anyone from sending more than 4GB of data.

I don't think 4 bytes size is any particular size "loss" for small packets to 
feel bad about, so I prefer the simplicity of always just getting the size in 
a single specified way.

> Its not the lazy coders who pay others net bills.

Uh?

-- 

  / daniel.haxx.se