IETF Logo Mail Archive

Re: [hybi] Is it important to know frame length at the start of frame? (was: Re: Discontinuation of mux ...)

Zhong Yu <zhong.j.yu@gmail.com> Mon, 24 February 2014 20:58 UTC

Return-Path: <zhong.j.yu@gmail.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A7AD1A0280 for <hybi@ietfa.amsl.com>; Mon, 24 Feb 2014 12:58:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OHlqf5Y46ifJ for <hybi@ietfa.amsl.com>; Mon, 24 Feb 2014 12:58:36 -0800 (PST)
Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com [IPv6:2607:f8b0:4003:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id 8FDF41A0257 for <hybi@ietf.org>; Mon, 24 Feb 2014 12:58:36 -0800 (PST)
Received: by mail-ob0-f177.google.com with SMTP id wp18so7716948obc.36 for <hybi@ietf.org>; Mon, 24 Feb 2014 12:58:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=sBcM4pv7oIM5DH7MxHm8XYDEHogffi9KDH+8jEezUM4=; b=tC4t2+GZ/a5lxUgUApiuCZFSZlkHoPrDh6BXk2sIl0mzdEIf3wBnq/kj1UDvGMk1Uw EVHh1/jGVucHH8Lj01oCtkFioD8pEkDoSi6miskPwqBfcVOQPkXV+g13xx2K2tYYfmYE O5F4FikFacWZwhlIQxJKKv8E7+/Iynbgc8AV37vGWO1UlUzTdhheeTX1W8acDimx0PjI Ovrmpkm84y5zJJqVsuTW5RUeKrA79CIJzSoso+nQCEsm0LTVF1NWcA5bhIfoUfIGqeWg OeJ8bEdXbYcuiMzLahmCk1DUcYxwESm9tgLByTmwF5cS7jnsDvbbVIM+5kQa6bh2R5N2 S0Wg==
MIME-Version: 1.0
X-Received: by 10.60.174.170 with SMTP id bt10mr23484871oec.47.1393275515870; Mon, 24 Feb 2014 12:58:35 -0800 (PST)
Received: by 10.76.106.162 with HTTP; Mon, 24 Feb 2014 12:58:35 -0800 (PST)
In-Reply-To: <CAGzyod767Aj5AeNF8yp4+Whm2kVrG_Dg0D7nechpbpa6G36Bqw@mail.gmail.com>
References: <CAH9hSJbf_ABT7ECL9eS=_ADrncX8qBtxZv=uLcdu9_6GUv23Uw@mail.gmail.com> <CACuKZqEcA1Pv8RpWfmThMjTzi2BbVMMKXqujs6BxVfxRPZJ9NQ@mail.gmail.com> <CAG4zZZCr4aTfVpw2coX2g0qw++4kdgNCFVze6tHKZ+fJNqb0aQ@mail.gmail.com> <CAG4zZZA4WR50Ea2e36XEgTgpJURwiMFn+DXeYuxHFfZatYzDOQ@mail.gmail.com> <CAH9hSJYv5VXGjS7AfG12-ArEvE6Uj_eE6pPxAiQcchcgV8vHcg@mail.gmail.com> <CAH9hSJbzra7uz7yfKQwfZaP_jhnxwdZyx8JnwCmBGhiMk6rbtg@mail.gmail.com> <CAG4zZZC1cmaH36znAvVLZE_MyJ+ThNk1Ky7tQ-QnKf_qwiQNDw@mail.gmail.com> <CAG4zZZB3h6TTFLUp-ucYQP7tMf-8=h5fh1UqufMh3w-0JN+hSw@mail.gmail.com> <CAH9hSJaeCrLjkhHUzaaGDw-apiSv-eaPZeYGEHBuwRoF3yPCOA@mail.gmail.com> <CAH9hSJY4NResx4DskJM8agd5ZXo9yHELYaXOpWG-xXK8P4+9zw@mail.gmail.com> <CACuKZqHTr0vufQr5mEHM2__NconW_d6jrzTpD0JKEzsiP09uwg@mail.gmail.com> <CAGzyod767Aj5AeNF8yp4+Whm2kVrG_Dg0D7nechpbpa6G36Bqw@mail.gmail.com>
Date: Mon, 24 Feb 2014 14:58:35 -0600
Message-ID: <CACuKZqGs+F_Jh7qatwCF7YoZ3qE6rBU5Vd2xzwLbn8eAc6+OtA@mail.gmail.com>
From: Zhong Yu <zhong.j.yu@gmail.com>
To: Roberto Peon <fenix@google.com>
Content-Type: text/plain; charset="ISO-8859-1"
Archived-At: http://mailarchive.ietf.org/arch/msg/hybi/j_PgGf_u9ddY9klOLUehsfygBJQ
Cc: "hybi@ietf.org" <hybi@ietf.org>, Peter Thorson <webmaster@zaphoyd.com>
Subject: Re: [hybi] Is it important to know frame length at the start of frame? (was: Re: Discontinuation of mux ...)
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 24 Feb 2014 20:58:38 -0000

Uh? I was talking about ws frames, not ws messages. We can always
break up big frames into small frames (unless frame boundary has any
semantics to anyone).

On Mon, Feb 24, 2014 at 2:39 PM, Roberto Peon <fenix@google.com> wrote:
> The browser API doesn't have a limit on the size of a message, so the layers
> below that API should probably support it.
> It would be incomplete not to, for sure.
>
> As for why someone would do it? Who knows. Perhaps someone is exploiting the
> fact that WS stuff never gets put into a cache for security reasons? Or
> perhaps because using the API is easier and better expresses the application
> semantics, even if they're not doing web browsing? Any of these seem
> reasonable. There is no requirement for WS to include only small messages...
>
> -=R
>
>
> On Mon, Feb 24, 2014 at 12:29 PM, Zhong Yu <zhong.j.yu@gmail.com> wrote:
>>
>> It there any problem if we mandate that 1 http frame corresponds to 1
>> ws frame, and 1 ws frame must reside in 1 http frame? What's the point
>> of supporting ws frames that need multiple http frames?
>>
>> On Mon, Feb 24, 2014 at 12:28 PM, Takeshi Yoshino <tyoshino@google.com>
>> wrote:
>> > Thanks all for your comments.
>> >
>> > First, please note that I wanted to discuss the question in the context
>> > of
>> > WS/HTTP/2.0 layering. Not about redesign of RFC 6455 itself.
>> >
>> > I asked this question since the length header is the biggest field when
>> > encoded into HTTP/2.0 HEADERS format. Whether we can eliminate it or not
>> > in
>> > WS/HTTP/2.0 is one of the most important points to evaluate the plans
>> > employing HTTP/2.0 HEADERS.
>> >
>> > Though the ranges the length headers represent differ (HTTP/2.0: 14 bit,
>> > WS
>> > length format: 63 bit), it seems everyone can live without a header of
>> > "original WebSocket frame size".
>> >
>> > Please reply to this post if you have any objection, but please don't
>> > write
>> > objection to use of HTTP/2.0 HEADERS itself in this thread.
>> >
>> > Thanks
>>
>> _______________________________________________
>> hybi mailing list
>> hybi@ietf.org
>> https://www.ietf.org/mailman/listinfo/hybi
>
>

v2.23.0 | Report a Bug | By Email