Re: [hybi] Support for sub-protocols on the WebSocket API?

John Tamplin <jat@google.com> Fri, 09 September 2011 18:52 UTC

Return-Path: <jat@google.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 2DDE621F8726 for <hybi@ietfa.amsl.com>; Fri, 9 Sep 2011 11:52:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.933
X-Spam-Level:
X-Spam-Status: No, score=-105.933 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 aYTRfIL6C9YS for <hybi@ietfa.amsl.com>; Fri, 9 Sep 2011 11:52:56 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by ietfa.amsl.com (Postfix) with ESMTP id 3DEB121F86F6 for <hybi@ietf.org>; Fri, 9 Sep 2011 11:52:56 -0700 (PDT)
Received: from wpaz21.hot.corp.google.com (wpaz21.hot.corp.google.com [172.24.198.85]) by smtp-out.google.com with ESMTP id p89Ism93031956 for <hybi@ietf.org>; Fri, 9 Sep 2011 11:54:49 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1315594489; bh=DThnDcO3A4M7iTp+HZlw6Ve7Uvg=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=wDbBSV/O4kDpXsFISyhOD5MDhHCnkmzXskXQ4NDQYrZvcn+gtJzi0ENO5nTd1BU6I m6+N9wkcaOYFoUyrQ4w7g==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:in-reply-to:references:from:date: message-id:subject:to:cc:content-type:x-system-of-record; b=Q7vUVPtxIy8SKW7RHljvXNYoHIp8yY/oo7aO69nv8zqsU/0iNiN665rLgLvHvJsoC zSBXpVTBPhFy5CRuGnS1g==
Received: from yxj19 (yxj19.prod.google.com [10.190.3.83]) by wpaz21.hot.corp.google.com with ESMTP id p89Isl7v022245 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <hybi@ietf.org>; Fri, 9 Sep 2011 11:54:47 -0700
Received: by yxj19 with SMTP id 19so1554607yxj.23 for <hybi@ietf.org>; Fri, 09 Sep 2011 11:54:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=mCJAT92oBZVQk/HaX3xQjYBV5T3CydfaWNPYICZHy0Y=; b=pSHHJ/g1RT1QIzcrAT6pdbZKby9ACzd0gtlTi93tSgTxUWdwQf6DA7hYhbDWIQJZHT eOwi2/Adq2SoyDFRdWuA==
Received: by 10.151.21.9 with SMTP id y9mr2277826ybi.344.1315594486286; Fri, 09 Sep 2011 11:54:46 -0700 (PDT)
Received: by 10.151.21.9 with SMTP id y9mr2277822ybi.344.1315594486114; Fri, 09 Sep 2011 11:54:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.49.7 with HTTP; Fri, 9 Sep 2011 11:54:26 -0700 (PDT)
In-Reply-To: <CAKF+bsprn9uB4WrM-Mr6fVr1UfkMOyK2C1py-QSd+2XA_6oONQ@mail.gmail.com>
References: <CAKF+bsoW1_EtzMBEMfRTnJ1PKdpRUGm44ju8TMNbe-xWdaSpLQ@mail.gmail.com> <CABLsOLBbD2k8aNwn-jBFAcCecrCGTENN-GD=UaJtDi3=akO18Q@mail.gmail.com> <CAKF+bsprn9uB4WrM-Mr6fVr1UfkMOyK2C1py-QSd+2XA_6oONQ@mail.gmail.com>
From: John Tamplin <jat@google.com>
Date: Fri, 09 Sep 2011 14:54:26 -0400
Message-ID: <CABLsOLA4EPg=zcqFa_y691UCqkZBP6wO6-C=AuDQLFM=6+qiUQ@mail.gmail.com>
To: Clebert Suconic <clebert.suconic@gmail.com>
Content-Type: multipart/alternative; boundary="000e0cd4b2d60368ee04ac86b6ce"
X-System-Of-Record: true
Cc: hybi@ietf.org
Subject: Re: [hybi] Support for sub-protocols on the WebSocket API?
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: Fri, 09 Sep 2011 18:52:57 -0000

On Fri, Sep 9, 2011 at 2:34 PM, Clebert Suconic
<clebert.suconic@gmail.com>wrote:

> What about session 11.8 on the websocket-protocol:
>
> http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-14#section-11.8
>
>
> If I wanted to create an extension (a sub-protocol), I would be able
> to use additional opcodes, right?
>
> Or there's another interpretation here?
>

An extension is not the same as a subprotocol -- extensions can define new
opcodes, subprotocols can't.  Think of subprotocols as a layer on top of
WebSockets.

You could define an extension and make it mandatory for your subprotocol.

-- 
John A. Tamplin
Software Engineer (GWT), Google