Re: [hybi] frame length encoding

"Shelby Moore" <shelby@coolpage.com> Sat, 21 August 2010 21:24 UTC

Return-Path: <shelby@coolpage.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 F40733A6925 for <hybi@core3.amsl.com>; Sat, 21 Aug 2010 14:24:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.12
X-Spam-Level:
X-Spam-Status: No, score=-2.12 tagged_above=-999 required=5 tests=[AWL=0.479, 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 D39j4NcV9HxH for <hybi@core3.amsl.com>; Sat, 21 Aug 2010 14:24:29 -0700 (PDT)
Received: from www5.webmail.pair.com (www5.webmail.pair.com [66.39.3.83]) by core3.amsl.com (Postfix) with SMTP id E93D23A67FE for <hybi@ietf.org>; Sat, 21 Aug 2010 14:24:28 -0700 (PDT)
Received: (qmail 59089 invoked by uid 65534); 21 Aug 2010 21:25:02 -0000
Received: from 121.97.54.174 ([121.97.54.174]) (SquirrelMail authenticated user shelby@coolpage.com) by sm.webmail.pair.com with HTTP; Sat, 21 Aug 2010 17:25:02 -0400
Message-ID: <224b9ed365bd78fd5e316b8cb5f3f837.squirrel@sm.webmail.pair.com>
In-Reply-To: <1282423311.2014.6.camel@tng>
References: <AANLkTimKbmcpgx8k0uXUWvCO=8w9pPrtV=3y4qh6363k@mail.gmail.com> <alpine.DEB.2.00.1008212037190.27211@tvnag.unkk.fr> <AANLkTinrsT+wV48nHvVW_1ChGYffkq7jisU2-PZnMyKg@mail.gmail.com> <alpine.DEB.2.00.1008212123460.27211@tvnag.unkk.fr> <20ef7ed5e135c57c1ee5a741658b9d98.squirrel@sm.webmail.pair.com> <1282423311.2014.6.camel@tng>
Date: Sat, 21 Aug 2010 17:25:02 -0400
From: Shelby Moore <shelby@coolpage.com>
To: Patrick McManus <mcmanus@ducksong.com>
User-Agent: SquirrelMail/1.4.20
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: Hybi <hybi@ietf.org>
Subject: Re: [hybi] frame length encoding
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: shelby@coolpage.com
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 21:24:30 -0000

[snip]

> 32 bits with chunking would be fine to accommodate zero copy.
>
> there are some folks that want to be able to send any message in one
> chunk for unrelated reasons.

How can they send in one chunk if their file size is greater than 32 bit
length, if you limit the size to 32bit?

If you had a typo above and meant that some folks want to send in smaller
chunks than the proposed 64bit, they would still be able to send in any
size chunks regardless how large (and up to the size) we make the maximum
size.