Re: [hybi] Interface for Large Frames

Iñaki Baz Castillo <ibc@aliax.net> Thu, 23 June 2011 11:47 UTC

Return-Path: <ibc@aliax.net>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9902C11E80C9 for <hybi@ietfa.amsl.com>; Thu, 23 Jun 2011 04:47:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.664
X-Spam-Level:
X-Spam-Status: No, score=-2.664 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TDmIVDUrtXLa for <hybi@ietfa.amsl.com>; Thu, 23 Jun 2011 04:47:26 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 055C811E8073 for <hybi@ietf.org>; Thu, 23 Jun 2011 04:47:25 -0700 (PDT)
Received: by qwc23 with SMTP id 23so1219120qwc.31 for <hybi@ietf.org>; Thu, 23 Jun 2011 04:47:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.7.212 with SMTP id e20mr1418915qce.192.1308829645252; Thu, 23 Jun 2011 04:47:25 -0700 (PDT)
Received: by 10.229.181.209 with HTTP; Thu, 23 Jun 2011 04:47:25 -0700 (PDT)
In-Reply-To: <4E03229F.9070409@gmail.com>
References: <20110622145847.ef1fc80126c74c6c202a919c41c7bb0b.c4cc844e80.wbe@email03.secureserver.net> <4E026A1C.2030603@warmcat.com> <1308827929.11268.63.camel@tot.local> <4E03229F.9070409@gmail.com>
Date: Thu, 23 Jun 2011 13:47:25 +0200
Message-ID: <BANLkTinmZR4Eyc4TbfHgyfnv=utnRP4Pdg@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Philipp Serafin <phil127@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: hybi@ietf.org
Subject: Re: [hybi] Interface for Large Frames
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Thu, 23 Jun 2011 11:47:26 -0000

2011/6/23 Philipp Serafin <phil127@gmail.com>om>:
> Hasn't XMLHTTPRequest basically the same problem?
> The current JS API for XHR makes it necessary for a browser to buffer
> the complete response before passing it on to the JS layer. There also
> don't seem to be any clear restrictions on the maximum size of a
> resource fetched via XHR.
> Maybe it could be useful to see how current browsers handle the edge
> case of very large XHR responses?

I expect the problem will be more in server side than in client side.

-- 
Iñaki Baz Castillo
<ibc@aliax.net>