Re: [hybi] Frame size

"Thomson, Martin" <Martin.Thomson@andrew.com> Sun, 18 April 2010 23:06 UTC

Return-Path: <Martin.Thomson@andrew.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 1710A3A68F0 for <hybi@core3.amsl.com>; Sun, 18 Apr 2010 16:06:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.543
X-Spam-Level:
X-Spam-Status: No, score=-0.543 tagged_above=-999 required=5 tests=[AWL=-0.544, BAYES_50=0.001]
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 i46RTYKE4wMn for <hybi@core3.amsl.com>; Sun, 18 Apr 2010 16:06:54 -0700 (PDT)
Received: from csmailgw2.commscope.com (csmailgw2.commscope.com [198.135.207.242]) by core3.amsl.com (Postfix) with ESMTP id C92183A68B6 for <hybi@ietf.org>; Sun, 18 Apr 2010 16:06:30 -0700 (PDT)
Received: from [10.86.20.103] ([10.86.20.103]:44853 "EHLO ACDCE7HC2.commscope.com") by csmailgw2.commscope.com with ESMTP id S217492Ab0DRXGW (ORCPT <rfc822; hybi@ietf.org>); Sun, 18 Apr 2010 18:06:22 -0500
Received: from SISPE7HC2.commscope.com (10.97.4.13) by ACDCE7HC2.commscope.com (10.86.20.103) with Microsoft SMTP Server (TLS) id 8.1.436.0; Sun, 18 Apr 2010 18:06:22 -0500
Received: from SISPE7MB1.commscope.com ([fe80::9d82:a492:85e3:a293]) by SISPE7HC2.commscope.com ([fe80::58c3:2447:f977:57c3%10]) with mapi; Mon, 19 Apr 2010 07:06:22 +0800
From: "Thomson, Martin" <Martin.Thomson@andrew.com>
To: Justin Erenkrantz <justin@erenkrantz.com>
Date: Mon, 19 Apr 2010 07:07:50 +0800
Thread-Topic: [hybi] Frame size
Thread-Index: AcrdOIE/PJsGGGrXT62ID1nxjBm95gCEpAYQ
Message-ID: <8B0A9FCBB9832F43971E38010638454F03E7D06790@SISPE7MB1.commscope.com>
References: <8B0A9FCBB9832F43971E38010638454F03E3F313ED@SISPE7MB1.commscope.com> <v2m5c902b9e1004160043i7b5ccc79y2346e1b2b2c55cf5@mail.gmail.com>
In-Reply-To: <v2m5c902b9e1004160043i7b5ccc79y2346e1b2b2c55cf5@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-BCN: Meridius 1000 Version 3.4 on csmailgw2.commscope.com
X-BCN-Sender: Martin.Thomson@andrew.com
Cc: Hybi <hybi@ietf.org>
Subject: Re: [hybi] Frame size
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: Sun, 18 Apr 2010 23:06:55 -0000

> >  - Frame size be strictly limited (2 octets should suffice).
> 
> To be clear, this would be 16-bits for the size or a max of 65,535
> bytes in a single frame, correct?
> 
> (I'm assuming that you don't mean "2 octets" as being that's all you
> can send in one frame.  *grin*)

Oh no, 2 octets is enough - it's twice as many as we currently use as the base unit for our other protocols.

Think of this as Web 2.0, in that the basic unit is 2.0 times the size of the previous version.
 
> a few folks talked about Comet
> apps they've seen transferring large XML files.  Silly perhaps, but
> that's what the app writers did...trying to get them to change is
> pointless.

On reflection, it really doesn't matter what the maximum allowable size is in the protocol.  I originally thought 16 bits would be great because that would be closer to what actual application limits would be - but then that's a little silly too.  If there is going to be a limit - I want that limit to be flexible too.  16 bits is just as arbitrary.  And, if folks want to shift big files this way, let's not be so hard on them.

Incidentally, you can get continuation frames for free: if any frame is full, the next one is a continuation.  If you happen to have a frame that is exactly 65535 octets long, then the next one can be exactly 0 octets long.

--Martin