IETF Logo Mail Archive

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

Takeshi Yoshino <tyoshino@google.com> Tue, 18 February 2014 05:38 UTC

Return-Path: <tyoshino@google.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 9D6AC1A02EE for <hybi@ietfa.amsl.com>; Mon, 17 Feb 2014 21:38:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.926
X-Spam-Level:
X-Spam-Status: No, score=-1.926 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.548, 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 9nqqpM4NmCC6 for <hybi@ietfa.amsl.com>; Mon, 17 Feb 2014 21:38:13 -0800 (PST)
Received: from mail-we0-x22f.google.com (mail-we0-x22f.google.com [IPv6:2a00:1450:400c:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 538B71A00D3 for <hybi@ietf.org>; Mon, 17 Feb 2014 21:38:13 -0800 (PST)
Received: by mail-we0-f175.google.com with SMTP id q59so11407289wes.34 for <hybi@ietf.org>; Mon, 17 Feb 2014 21:38:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=VVg5d0ZjWln0QEZJkQoaqzqZkWTumWTJd8NWwi+OPZI=; b=PwE3b2zmx7KjbyufyFMTb/qZ0NdQo+X1C+9mLXBLY6HxAZFjOEunNC566pXDFCPLeN XdAjEEYckCUCJ3qkb3OjIiy7s58wl24mmpFa+81EIYgqF3PKoWxaXz5Om2dgslEH/1K4 po7m4cDyNDyfzZ2tcE7GEMS4qJBpMLT3mUFMLcVdMyGjZw4Ryvi3bgiPiQHE6/CY9y+p QbTFrXwUSPWricVDIK+5TrWOQjv+im9s3LaucBLL4hAWlf/jpggp2TEA5fn/C0jIvQAz V4hVbOGlZILiCykRi5eofIZGHBh3YciM+Ddr/0vFFKwux+seqS4jNpTWlRUakbAwQiaN nDcg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=VVg5d0ZjWln0QEZJkQoaqzqZkWTumWTJd8NWwi+OPZI=; b=B2Ehx132iCTl+94vYGC/5LVeiR9/vYbX5Z3dvg1EDrKwwoWrdfAD5pP+1X+oF1HNhK xg4j78VBLHy1MZZzXybGPhCOzevUaEkEuVzr3leR6hcUMTqbu6rFURnuWQqVRYrQvf0q NN2cHiDKv6y9ndlSksfY9BLJqgx85WkTdTf/4M24Hyog+gYgKcN2s9eAKI39bA4XIn8S UMYhGsAam4WsYFQFc9e65jQhc35SXLGwZdYDB+Q8snMDAgK6shMWSEk3+HSVgK5ZYYNf uyJsIZQMIV49bkthg9PLvGYR5sweULjCvgtBlBksjhBIc+jwwg6TeiFU9EOJ64tfSZvH 6+CQ==
X-Gm-Message-State: ALoCoQlOWpP6CUc5HLCfKP63KnM++dBFwkYxoDEGEGArgPFjD7Q7WV7YhIIKdvEIuDUSdS65tgpdO2ZghhTnpiX6LsO2wh1F50wcKEc3wKwceHPQo8xiAYhXgJgyJ/+X2WbmU56E9NbjUeFdM5px/gGzi63fp3/BWkUz5asI+OacpcIZRg5BPx9agPgI6iORiESju87jpVj2
X-Received: by 10.181.13.11 with SMTP id eu11mr15802442wid.30.1392701890086; Mon, 17 Feb 2014 21:38:10 -0800 (PST)
MIME-Version: 1.0
Received: by 10.194.8.231 with HTTP; Mon, 17 Feb 2014 21:37:49 -0800 (PST)
In-Reply-To: <CAH9hSJYv5VXGjS7AfG12-ArEvE6Uj_eE6pPxAiQcchcgV8vHcg@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>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Tue, 18 Feb 2014 14:37:49 +0900
Message-ID: <CAH9hSJbzra7uz7yfKQwfZaP_jhnxwdZyx8JnwCmBGhiMk6rbtg@mail.gmail.com>
To: Joakim Erdfelt <joakim@intalio.com>
Content-Type: multipart/alternative; boundary="f46d043c7de66ff11404f2a7ad17"
Archived-At: http://mailarchive.ietf.org/arch/msg/hybi/zHEPAxwRXjZzJrPJzSRRwXOgl3Q
Cc: "hybi@ietf.org" <hybi@ietf.org>
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: Tue, 18 Feb 2014 05:38:15 -0000

So, to be clear, Joakim, you're not objecting to make it unable to know the
size of each frame, but objecting to make it completely unable to know the
size of big messages on receiving the head of it, right?

Your use case (fail-fast) seems to require the sender to send messages
unfragmented. So, it sounds like application (or kind of application)
specific needs. You could do some application specific hack such as
introducing "complete-message-size" header in the payload than depending on
protocol level length header. If not, clients in the wild which are out of
your control may do arbitrary fragmentation. FYI, Chromium's WebSocket
stack is being refactored and after that it starts sending big messages as
fragmented into small frames.

v2.23.0 | Report a Bug | By Email