IETF Logo Mail Archive

Re: [hybi] Framing take IV [why fragment]

Greg Wilkins <gregw@webtide.com> Thu, 05 August 2010 22:51 UTC

Return-Path: <gregw@webtide.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 6A68C3A6907 for <hybi@core3.amsl.com>; Thu, 5 Aug 2010 15:51:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.742
X-Spam-Level:
X-Spam-Status: No, score=-1.742 tagged_above=-999 required=5 tests=[AWL=0.235, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 dDQJfJQI-iVW for <hybi@core3.amsl.com>; Thu, 5 Aug 2010 15:51:21 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 3315E3A68DD for <hybi@ietf.org>; Thu, 5 Aug 2010 15:51:21 -0700 (PDT)
Received: by fxm16 with SMTP id 16so2846744fxm.31 for <hybi@ietf.org>; Thu, 05 Aug 2010 15:51:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.120.82 with SMTP id c18mr11601806far.69.1281048710879; Thu, 05 Aug 2010 15:51:50 -0700 (PDT)
Received: by 10.223.57.12 with HTTP; Thu, 5 Aug 2010 15:51:50 -0700 (PDT)
In-Reply-To: <2286.1281023493.052316@puncture>
References: <AANLkTinyrDoG5d_Ur6HVRy=SgMPjLzJtpJ++Ye=1DQdj@mail.gmail.com> <Pine.LNX.4.64.1008040050040.5947@ps20323.dreamhostps.com> <1280932393.7561.271.camel@tng> <2286.1281017237.786534@puncture> <AANLkTimWeL5Td0_H0+q+p=CpPqy-GAdhiKxqr5yyGNzL@mail.gmail.com> <2286.1281023493.052316@puncture>
Date: Fri, 06 Aug 2010 08:51:50 +1000
Message-ID: <AANLkTim3BVVLcTbq0eiwkfyrqjNR5qOVO2pqbwP+sqhe@mail.gmail.com>
From: Greg Wilkins <gregw@webtide.com>
To: Dave Cridland <dave@cridland.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: Server-Initiated HTTP <hybi@ietf.org>
Subject: Re: [hybi] Framing take IV [why fragment]
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: Thu, 05 Aug 2010 22:51:22 -0000

On 6 August 2010 01:51, Dave Cridland <dave@cridland.net> wrote:
> On Thu Aug  5 16:38:58 2010, John Tamplin wrote:
>>
>> On Thu, Aug 5, 2010 at 10:07 AM, Dave Cridland <dave@cridland.net> wrote:
>>
>> > On Wed Aug  4 15:33:13 2010, Patrick McManus wrote:
>>
>> For per-frame compression, you certainly can decompress each chunk as you
>> receive it.  Yes, the JS API currently does not have a way to pass partial
>> messages, and perhaps that needs to get fixed when binary support is added
>> since it seems more likely you will want to be able to react to partial
>> messages as each part is received.
>
> I think the definition of a message is something that an application
> programmer can sensibly write code to react to, so I'd disagree.

I agree -  a message by definition is the smallest entity that should
be passed to an application.
An application is free to have their own idea of partial content and
to work on a stream of messages.

Frames are the mechanism that the transport layer uses to simplify and
optimize transport and should be entirely transparent to the
application, hence it should not be done in a sub protocol.   TCP has
it's own framing and applications may repeat this pattern for their
own efficiencies etc   (It's turtles all the way down ).

cheers

v2.23.0 | Report a Bug | By Email