Re: [hybi] Frame size

Jamie Lokier <jamie@shareable.org> Mon, 19 April 2010 01:01 UTC

Return-Path: <jamie@shareable.org>
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 F31DD3A6931 for <hybi@core3.amsl.com>; Sun, 18 Apr 2010 18:01:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.519
X-Spam-Level:
X-Spam-Status: No, score=-2.519 tagged_above=-999 required=5 tests=[AWL=-1.780, BAYES_20=-0.74]
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 6dgZxDeDjbOW for <hybi@core3.amsl.com>; Sun, 18 Apr 2010 18:01:51 -0700 (PDT)
Received: from mail2.shareable.org (mail2.shareable.org [80.68.89.115]) by core3.amsl.com (Postfix) with ESMTP id AAE193A68A0 for <hybi@ietf.org>; Sun, 18 Apr 2010 18:01:46 -0700 (PDT)
Received: from jamie by mail2.shareable.org with local (Exim 4.63) (envelope-from <jamie@shareable.org>) id 1O3fMm-0005P3-Vl; Mon, 19 Apr 2010 02:01:36 +0100
Date: Mon, 19 Apr 2010 02:01:36 +0100
From: Jamie Lokier <jamie@shareable.org>
To: Justin Erenkrantz <justin@erenkrantz.com>
Message-ID: <20100419010136.GE18876@shareable.org>
References: <8B0A9FCBB9832F43971E38010638454F03E3F313ED@SISPE7MB1.commscope.com> <v2m5c902b9e1004160043i7b5ccc79y2346e1b2b2c55cf5@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <v2m5c902b9e1004160043i7b5ccc79y2346e1b2b2c55cf5@mail.gmail.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
Cc: Hybi <hybi@ietf.org>, "Thomson, Martin" <Martin.Thomson@andrew.com>
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: Mon, 19 Apr 2010 01:01:52 -0000

Justin Erenkrantz wrote:
> 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.

Silly, few?  Most AJAX requesting code I've seen fetches a bit of HTML
to replace in an existing page, such as replacing a DIV or table row,
or the main area in a page (i.e. the bit which isn't border buttons
etc.)  That's easily a megabyte of response in many web pages...
It's hard to see why Comet would avoid that pattern.

Every so often, someone says that big requests should not be using
WebSocket but should go out of line, using HTTP.

But if you can send a large blob of text over WebSocket, why would
anyone *not* do that?  The effects of receiving a short update message
over WebSocket and then issuing a long HTTP request are twofold:

   - More complicated application code (unnecessary)
   - Higher latency (extra round trip + possible DNS, TCP, SSL setup)

It follows that sending large messages over WebSocket is perfectly
natural and might be best, if the alternative is to get the same large
message over HTTP using XmlHttpRequest.

-- Jamie