IETF Logo Mail Archive

Re: [hybi] Call for interest: multiplexing dedicated for WebSocket

Joakim Erdfelt <joakim@intalio.com> Wed, 22 May 2013 15:33 UTC

Return-Path: <joakim@intalio.com>
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 3707121F84A6 for <hybi@ietfa.amsl.com>; Wed, 22 May 2013 08:33:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qJReH3zJdlig for <hybi@ietfa.amsl.com>; Wed, 22 May 2013 08:33:20 -0700 (PDT)
Received: from mail-ea0-x232.google.com (mail-ea0-x232.google.com [IPv6:2a00:1450:4013:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id 4709321F9118 for <hybi@ietf.org>; Wed, 22 May 2013 08:33:15 -0700 (PDT)
Received: by mail-ea0-f178.google.com with SMTP id q16so1232195ead.23 for <hybi@ietf.org>; Wed, 22 May 2013 08:33:15 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=nX64Lb458TnlAwWlTWgJApfAYlnUabKnaT9PRv00dN8=; b=f2iiybVFjv6AAdI5WHGgUCNehvYBwdpVj8h2flhOnaBDqRKUIxtta137UnKLSNKXJ3 x/huAixA3jDCGDSGJc+3STAv3euqfz62btAvYCg7jRz6U76g8Ia7Vp5CDOuTHTDCqSd/ rjDc1HLEa57HxP9GpJvtDCa5k8aDGohjL4GheMvDc0GN5OBNQ0o6DARekDrCZs3vkqsR IwV4q/6KiSwDWKB9reZith8b9I7fzViQlC8X+mx3BiqdxBF9jhFl0ZawT/CSabvvGGyS 0wXRs9BiCJwr0Y4upLezJ3eGftabGmmpcZbQZnXjF1faDLskMnLL4gkhI8M/brN4MlP5 j/Cw==
MIME-Version: 1.0
X-Received: by 10.15.107.77 with SMTP id ca53mr19743217eeb.40.1369236795074; Wed, 22 May 2013 08:33:15 -0700 (PDT)
Received: by 10.15.32.8 with HTTP; Wed, 22 May 2013 08:33:14 -0700 (PDT)
In-Reply-To: <007501ce56f0$67f74080$37e5c180$@noemax.com>
References: <CAH9hSJZxr+aG7GZa4f-dUOTGj4bnJ+3XxivUX4jei5CMyqN4LQ@mail.gmail.com> <CAH9hSJZUG1f+3Uk=t2=A5i4O9=wPvAisspM=pgmGEH9emTL9-Q@mail.gmail.com> <CAH9hSJZai_UuxW4O6mZcEJT2DJoURtLo16XNci1qkYVWv4HVdg@mail.gmail.com> <007501ce56f0$67f74080$37e5c180$@noemax.com>
Date: Wed, 22 May 2013 08:33:14 -0700
Message-ID: <CAG4zZZBpL3=szF6R80SHJeSTYig-bKe8cDPeJS=r2j4Z5oJ_NQ@mail.gmail.com>
From: Joakim Erdfelt <joakim@intalio.com>
To: Arman Djusupov <arman@noemax.com>
Content-Type: multipart/alternative; boundary="089e0162830cc8d94404dd504832"
X-Gm-Message-State: ALoCoQmbH8Qw59WO5OUrtE7AVG61O2fElCLJ4zCFFwf7GyfpLe24NDxrFDLwi+MIF402rOZQuSLH
Cc: hybi@ietf.org
Subject: Re: [hybi] Call for interest: multiplexing dedicated for WebSocket
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: Wed, 22 May 2013 15:33:21 -0000

+1 for simplification.

I'll toss some topics onto the table now:
 * AddChannelRequest - eliminate header deltas
 * AddChannelResponse - eliminate header deltas
 * NewChannelSlot - eliminate the "channel slots" management entirely from
the spec, go back to the earlier, easier to implement, concepts from past
drafts.
 * Simplify the extension rules.
     Extensions after initial physical connection are applied only to first
logical channel.
     in AddChannelRequest, extensions provided after the mux extension are
used for logical channels.



--
Joakim Erdfelt <joakim@intalio.com>
webtide.com <http://www.webtide.com/>
Developer advice, services and support
from the Jetty & CometD experts
eclipse.org/jetty - cometd.org


On Wed, May 22, 2013 at 6:29 AM, Arman Djusupov <arman@noemax.com> wrote:

> Sorry, just realized that my message was sent to Takeshi privately by
> mistake a few days ago.. (wrong button). It was actually intended for the
> list so I am repeating it publicly now:****
>
> ** **
>
> ** **
>
> Obviously continuing to develop a hybi-mux spec for another year or two
> doesn’t make sense. Taking into account that new specifications are coming
> and that HTTP2.0 will probably provide multiplexing for both WebSocket and
> HTTP traffic, at  this stage it would only be worth investing development
> time in a “simple and ready to go” hybi-mux specification. Maybe if we
> simplify the spec to rock bottom simplicity, even sacrificing some features
> so that we can conclude it very fast, then maybe vendors might pick it up.
> This way we will give to WebSocket its own mux for now, while the HTTPbis
> draft might take much longer to form into the final specification. In any
> case, hybi-mux must be reviewed and finalized in a very short time, plus it
> should be simpler and easier to implement than both SDPY and HTTPbis based
> multiplexing.****
>
> ** **
>
> With best regards,****
>
> Arman****
>
> ** **
>
> *From:* hybi-bounces@ietf.org [mailto:hybi-bounces@ietf.org] *On Behalf
> Of *Takeshi Yoshino
> *Sent:* Sunday, May 19, 2013 7:31 AM
> *To:* hybi@ietf.org
> *Subject:* Re: [hybi] Call for interest: multiplexing dedicated for
> WebSocket****
>
> ** **
>
> I got one comment about this.****
>
> ** **
>
> He/she suggested that we finish the WebSocket dedicated multiplexing
> quickly even by simplifying the spec much e.g. cutting some functionality
> in it that would take much time to get consensus, and when HTTP/2.0 is
> matured, switch to that.****
>
>  ****
>
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>
>

v2.23.0 | Report a Bug | By Email