Re: [hybi] Multiplexing extension spec draft 03
"Arman Djusupov" <arman@noemax.com> Tue, 27 March 2012 10:42 UTC
Return-Path: <arman@noemax.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 ECC2821E817A for <hybi@ietfa.amsl.com>; Tue, 27 Mar 2012 03:42:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.236
X-Spam-Level:
X-Spam-Status: No, score=-1.236 tagged_above=-999 required=5 tests=[AWL=-1.052, BAYES_40=-0.185, HTML_MESSAGE=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 aB07PIFCgC2G for <hybi@ietfa.amsl.com>; Tue, 27 Mar 2012 03:42:02 -0700 (PDT)
Received: from mail.noemax.com (mail.noemax.com [64.34.201.8]) by ietfa.amsl.com (Postfix) with ESMTP id B84C421E8179 for <hybi@ietf.org>; Tue, 27 Mar 2012 03:42:01 -0700 (PDT)
Received: from vista1 by mail.noemax.com (IceWarp 9.4.1) with ASMTP (SSL) id LNQ34255; Tue, 27 Mar 2012 13:41:55 +0300
From: Arman Djusupov <arman@noemax.com>
To: 'Takeshi Yoshino' <tyoshino@google.com>
References: <CAH9hSJb1ewPO3EBgD78anD+=4XouToGR4X7C1wvWqonc2nYB6g@mail.gmail.com> <000301cd05dd$c8f9fc70$5aedf550$@noemax.com> <CAH9hSJYni6BboWdjkLX9xsguph7wJwjAmTUD1genFzT0ja5Wdw@mail.gmail.com> <003b01cd08d8$b1dd7050$159850f0$@noemax.com> <CAH9hSJYmL1ngaEJ1Th1kye2WKvJ4-zup1qbHCPLs+6MBOtS4Fg@mail.gmail.com> <CAH9hSJa7RQz=kreweLNH15ZpSHu3jZ1fRNOJXOmcy-v_SkmtKA@mail.gmail.com>
In-Reply-To: <CAH9hSJa7RQz=kreweLNH15ZpSHu3jZ1fRNOJXOmcy-v_SkmtKA@mail.gmail.com>
Date: Tue, 27 Mar 2012 13:41:54 +0300
Message-ID: <000d01cd0c06$3defdf80$b9cf9e80$@noemax.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_000E_01CD0C1F.633D1780"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJyksDj69tXg0EBn6jyTi4rbdnguwGRJ3ibAhBToZcCh7t1pgGkm8LGAf86ZtaU5H3tUA==
Content-Language: en-us
Cc: hybi@ietf.org
Subject: Re: [hybi] Multiplexing extension spec draft 03
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: Tue, 27 Mar 2012 10:42:04 -0000
The sample is OK. But it would add complexity to the handshake. On the positive side what we get as a result of such communication is actually named-channels. So the API can specify a channel by name e.g. socket["voice"].send(data) . I would also like to read more opinions on this. With best regards, Arman From: Takeshi Yoshino [mailto:tyoshino@google.com] Sent: Saturday, March 24, 2012 4:56 AM To: Arman Djusupov Cc: hybi@ietf.org Subject: Re: [hybi] Multiplexing extension spec draft 03 On Sat, Mar 24, 2012 at 03:57, Takeshi Yoshino <tyoshino@google.com> wrote: How about this, for example? C->S Sec-WebSocket-Extensions: mux; preopen="vc-video, vc-voice, vc-control, vc-subtitle" (each comma-separated element in preopen parameter's value means value of Sec-WebSocket-Protocol) S->C Sec-WebSocket-Extensions: mux; preopen="vc-video=1, vc-voice=2, vc-control=3, vc-subtitle=4" and the server sends back 4 AddChannel responses. Sorry. This example was wrong. C->S - Sec-WebSocket-Extensions: mux; add="vc-video=1, vc-voice=2, vc-control=3, vc-subtitle=4" (Format: <subprotocol>=<channel ID>) S->C - Sec-WebSocket-Extensions: mux; add="vc-video, vc-voice, vc-control, vc-subtitle" - 4 AddChannel responses
- [hybi] Multiplexing extension spec draft 03 Takeshi Yoshino
- Re: [hybi] Multiplexing extension spec draft 03 Tobias Oberstein
- Re: [hybi] Multiplexing extension spec draft 03 Takeshi Yoshino
- Re: [hybi] Multiplexing extension spec draft 03 Tobias Oberstein
- Re: [hybi] Multiplexing extension spec draft 03 John Tamplin
- Re: [hybi] Multiplexing extension spec draft 03 Tobias Oberstein
- Re: [hybi] Multiplexing extension spec draft 03 Julian Reschke
- Re: [hybi] Multiplexing extension spec draft 03 Greg Wilkins
- Re: [hybi] Multiplexing extension spec draft 03 Joakim Erdfelt
- Re: [hybi] Multiplexing extension spec draft 03 John Tamplin
- Re: [hybi] Multiplexing extension spec draft 03 Takeshi Yoshino
- Re: [hybi] Multiplexing extension spec draft 03 Takeshi Yoshino
- Re: [hybi] Multiplexing extension spec draft 03 John Tamplin
- Re: [hybi] Multiplexing extension spec draft 03 Greg Wilkins
- Re: [hybi] Multiplexing extension spec draft 03 John Tamplin
- Re: [hybi] Multiplexing extension spec draft 03 Greg Wilkins
- Re: [hybi] Multiplexing extension spec draft 03 Arman Djusupov
- Re: [hybi] Multiplexing extension spec draft 03 Takeshi Yoshino
- Re: [hybi] Multiplexing extension spec draft 03 Arman Djusupov
- Re: [hybi] Multiplexing extension spec draft 03 Arman Djusupov
- Re: [hybi] Multiplexing extension spec draft 03 Takeshi Yoshino
- Re: [hybi] Multiplexing extension spec draft 03 Arman Djusupov
- Re: [hybi] Multiplexing extension spec draft 03 Takeshi Yoshino
- Re: [hybi] Multiplexing extension spec draft 03 Takeshi Yoshino
- Re: [hybi] Multiplexing extension spec draft 03 Arman Djusupov
- Re: [hybi] Multiplexing extension spec draft 03 Arman Djusupov
- Re: [hybi] Multiplexing extension spec draft 03 Takeshi Yoshino
- Re: [hybi] Multiplexing extension spec draft 03 Arman Djusupov
- Re: [hybi] Multiplexing extension spec draft 03 John Tamplin
- Re: [hybi] Multiplexing extension spec draft 03 Takeshi Yoshino
- Re: [hybi] Multiplexing extension spec draft 03 Takeshi Yoshino
- Re: [hybi] Multiplexing extension spec draft 03 Takeshi Yoshino
- Re: [hybi] Multiplexing extension spec draft 03 John Tamplin
- Re: [hybi] Multiplexing extension spec draft 03 Arman Djusupov