IETF Logo Mail Archive

Re: [hybi] Fwd: The MessageBroker WebSocket Subprotocol

Brian <theturtle32@gmail.com> Mon, 03 October 2011 05:34 UTC

Return-Path: <theturtle32@gmail.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 D6C2521F8508 for <hybi@ietfa.amsl.com>; Sun, 2 Oct 2011 22:34:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.508
X-Spam-Level:
X-Spam-Status: No, score=-3.508 tagged_above=-999 required=5 tests=[AWL=0.090, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 Zr8T+BjGxm18 for <hybi@ietfa.amsl.com>; Sun, 2 Oct 2011 22:34:28 -0700 (PDT)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1685821F8505 for <hybi@ietf.org>; Sun, 2 Oct 2011 22:34:27 -0700 (PDT)
Received: by bkaq10 with SMTP id q10so5323499bka.31 for <hybi@ietf.org>; Sun, 02 Oct 2011 22:37:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=i5q6aepN2wtkyFykz1pBR6ok1R7aWEwqZ0j4CXsOhvs=; b=hq5mdckn8c7vQgHFqhdsrSZYvL2C6AkASvVfQ7izBbdDaBPjzeRXZr9X8osjSWNSE8 46mYRLF/K5qYUNyzfFjPdFeskvlvdDehRYyeXOxeICGKSNxQznDe/pLhkCxIw7JhqR0c HXepkJUkeJEB8mJq0UIBbvDzJkOHCkBZFk7Ik=
MIME-Version: 1.0
Received: by 10.204.156.66 with SMTP id v2mr8185094bkw.7.1317620248680; Sun, 02 Oct 2011 22:37:28 -0700 (PDT)
Received: by 10.204.152.129 with HTTP; Sun, 2 Oct 2011 22:37:28 -0700 (PDT)
In-Reply-To: <CAH_y2NH0KRi_mdvOQScFJtdWmKfFCk-g7C7F3e-xTYwA5C2CSw@mail.gmail.com>
References: <92457F4F764A5C4785FCDBDDDD76477A123C1C1A@dfweml506-mbx> <4E88236E.4040405@ericsson.com> <CABLsOLADfORBHVfPax75sQeRXTmTav8aOMfey_+KuSO=oPLsEA@mail.gmail.com> <4E88AB8D.6050407@callenish.com> <CAH_y2NH0KRi_mdvOQScFJtdWmKfFCk-g7C7F3e-xTYwA5C2CSw@mail.gmail.com>
Date: Sun, 02 Oct 2011 22:37:28 -0700
Message-ID: <CAE8AN_VLbyQfuf8Aq=fiW6L-7oDsA5d2GwkVq1fYYndofZ9-PQ@mail.gmail.com>
From: Brian <theturtle32@gmail.com>
To: Greg Wilkins <gregw@intalio.com>
Content-Type: multipart/alternative; boundary="0015175cb654df18be04ae5e5ee9"
Cc: "hybi@ietf.org" <hybi@ietf.org>, Hapner mark <hapner.mark@huawei.com>
Subject: Re: [hybi] Fwd: The MessageBroker WebSocket Subprotocol
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: Mon, 03 Oct 2011 05:34:28 -0000

On Sun, Oct 2, 2011 at 5:45 PM, Greg Wilkins <gregw@intalio.com> wrote:

> I do not think  opcodes are the right fit for defining messages in a
>
subprotocol (at least not in the ws protocol as we have designed it).
>

Absolutely correct.  Opcodes are not meant to be usable by subprotocols,
only extensions.  Any subprotocol that wants its own opcode must encode it
somewhere in the application data area of the WebSocket message.

Brian

v2.23.0 | Report a Bug | By Email