Re: [hybi] Support for sub-protocols on the WebSocket API?
John Tamplin <jat@google.com> Tue, 06 September 2011 21:40 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 44D4D21F8F05 for <hybi@ietfa.amsl.com>; Tue, 6 Sep 2011 14:40:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.878
X-Spam-Level:
X-Spam-Status: No, score=-105.878 tagged_above=-999 required=5 tests=[AWL=0.098, 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 pjB-2z8yVyI6 for <hybi@ietfa.amsl.com>; Tue, 6 Sep 2011 14:40:47 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by ietfa.amsl.com (Postfix) with ESMTP id B809D21F8E67 for <hybi@ietf.org>; Tue, 6 Sep 2011 14:40:47 -0700 (PDT)
Received: from wpaz29.hot.corp.google.com (wpaz29.hot.corp.google.com [172.24.198.93]) by smtp-out.google.com with ESMTP id p86LgYhB029301 for <hybi@ietf.org>; Tue, 6 Sep 2011 14:42:34 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1315345354; bh=lyG573MAcdb3x6t8QVacdPuO+mg=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=KBypRB6iVVHYYdHhLD0O5HRyDmnMeCVet+IgJYPLbAAtNdBqZQ7xZm07/5laOC/za zJHdzUQePXVfzhBzXGAsA==
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=xt7QLHcAr6Ym/V1CAq3lKnoMPObjpnzGLVK8ET6HE1lZKtYITHhRvEK+UCRalXQof IdYhiIuCSrpV7XDxN4lnA==
Received: from yia27 (yia27.prod.google.com [10.243.65.27]) by wpaz29.hot.corp.google.com with ESMTP id p86Lg0PA022483 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <hybi@ietf.org>; Tue, 6 Sep 2011 14:42:33 -0700
Received: by yia27 with SMTP id 27so6616691yia.30 for <hybi@ietf.org>; Tue, 06 Sep 2011 14:42:33 -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=fQBnShH50Qv9W1m40GRdv3qRC6ycUNJkAprl8gHtx0s=; b=fk/vpEHkwNbLH3zHKflY1ndo4N0kJ+8FPf3ywq088cp06yxDCLZTdzSP5lXhWQ8siR 1l33k9a238fgvyRWWCeQ==
Received: by 10.150.253.9 with SMTP id a9mr4214040ybi.230.1315345353282; Tue, 06 Sep 2011 14:42:33 -0700 (PDT)
Received: by 10.150.253.9 with SMTP id a9mr4214032ybi.230.1315345353134; Tue, 06 Sep 2011 14:42:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.49.7 with HTTP; Tue, 6 Sep 2011 14:42:13 -0700 (PDT)
In-Reply-To: <CAKF+bsoW1_EtzMBEMfRTnJ1PKdpRUGm44ju8TMNbe-xWdaSpLQ@mail.gmail.com>
References: <CAKF+bsoW1_EtzMBEMfRTnJ1PKdpRUGm44ju8TMNbe-xWdaSpLQ@mail.gmail.com>
From: John Tamplin <jat@google.com>
Date: Tue, 06 Sep 2011 17:42:13 -0400
Message-ID: <CABLsOLBbD2k8aNwn-jBFAcCecrCGTENN-GD=UaJtDi3=akO18Q@mail.gmail.com>
To: Clebert Suconic <clebert.suconic@gmail.com>
Content-Type: multipart/alternative; boundary="001517475c9287d15d04ac4cb4b4"
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: Tue, 06 Sep 2011 21:40:48 -0000
On Tue, Sep 6, 2011 at 5:39 PM, Clebert Suconic <clebert.suconic@gmail.com>wrote: > I was looking for a way to send a custom opcode on a subprotocol, ... > A subprotocol does not allow you to define new opcodes -- you can however, define how those payloads are to be interpreted (ie, send everything as OPCODE_BINARY, and then process it how you like). -- John A. Tamplin Software Engineer (GWT), Google
- [hybi] Support for sub-protocols on the WebSocket… Clebert Suconic
- Re: [hybi] Support for sub-protocols on the WebSo… John Tamplin
- Re: [hybi] Support for sub-protocols on the WebSo… Clebert Suconic
- Re: [hybi] Support for sub-protocols on the WebSo… John Tamplin
- Re: [hybi] Support for sub-protocols on the WebSo… Clebert Suconic
- Re: [hybi] Support for sub-protocols on the WebSo… Takeshi Yoshino
- Re: [hybi] Support for sub-protocols on the WebSo… Clebert Suconic
- Re: [hybi] Support for sub-protocols on the WebSo… John Tamplin
- Re: [hybi] Support for sub-protocols on the WebSo… Takeshi Yoshino