Re: [hybi] Requirement: extensions and sub protocols
KOMATSU Kensaku <kensaku.komatsu@gmail.com> Thu, 04 March 2010 01:32 UTC
Return-Path: <kensaku.komatsu@gmail.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0CFD23A8383 for <hybi@core3.amsl.com>; Wed, 3 Mar 2010 17:32:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9HVww3FBfxVS for <hybi@core3.amsl.com>; Wed, 3 Mar 2010 17:32:14 -0800 (PST)
Received: from mail-px0-f192.google.com (mail-px0-f192.google.com [209.85.216.192]) by core3.amsl.com (Postfix) with ESMTP id 0B88C3A68ED for <hybi@ietf.org>; Wed, 3 Mar 2010 17:32:11 -0800 (PST)
Received: by pxi30 with SMTP id 30so1543423pxi.17 for <hybi@ietf.org>; Wed, 03 Mar 2010 17:32:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=3q5b1jOnhRz+ACb7/0+PB4VGx8WCqgqsddOWQeKaVkI=; b=pQgXklmc6fzvaFuoGgQfULsmUKgdrd+FSULtjCaC4jfEdpfORDPRY1SkcBb7YhGB00 CMDTCSxnJvfmrFRxtIJLAJ9ZKJ0JnG+BwbZkEk7X5ZzAFzPJknWM/NXi0XtrnYtLAni8 TW5g5IutU0atzageY5sUyrEudwu/1FfAU2OpY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=ZhcdtK5Uf+4JSkgPLKfsIgOyHKwuR22glUxOdBmk1xOzTzrZVaeMyN9GluvCL0RL2L qscjWv0ehFFc1yia0+/JAh3wgjn4AxKknaEEjWoQKZvTn4d3IB5gy50hNdrg6QbR1W0V xfD+109EIv8jsmFU2FjJB/nw10uu9vfrPNkQ8=
MIME-Version: 1.0
Received: by 10.141.23.20 with SMTP id a20mr4719142rvj.193.1267666323206; Wed, 03 Mar 2010 17:32:03 -0800 (PST)
In-Reply-To: <4B8ECA2D.4050303@ericsson.com>
References: <4B8ECA2D.4050303@ericsson.com>
Date: Thu, 04 Mar 2010 10:32:03 +0900
Message-ID: <8e7c686d1003031732wa39f448k1d9286585517c0d8@mail.gmail.com>
From: KOMATSU Kensaku <kensaku.komatsu@gmail.com>
To: Salvatore Loreto <salvatore.loreto@ericsson.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: Hybi <hybi@ietf.org>
Subject: Re: [hybi] Requirement: extensions and sub protocols
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 04 Mar 2010 01:32:15 -0000
RTT measurements between client and server will be required for some extensions or sub-protocol. For example, TCP flow-control is so sensitive both content-size and RTT, so these two-parameters will be useful for some application's negotiation-phase which is better to use multiplexing frames in one channel or to use independent channels for each frames. Sincerly --- Kensaku KOMATSU 2010/3/4 Salvatore Loreto <salvatore.loreto@ericsson.com>: > Hi, > > another aspect of the WebSocket protocol we have to discuss is > extensibility. > As usual here a strawman proposal just to start the discussion... > > > Req. The WebSocket Protocol MUST be designed to easily support extensions. > > Req. The WebSocket Protocol MUST have a way to declare/negotiate extensions. > > Req. The WebSocket Protocol MUST be designed to easily support sub protocols > > Req. It SHOULD be easy for sub protocols implementing features like > channels, multiplexing, (what else?) > > please discuss extensions and subprotocols requirements (and feel free to > suggest better text) > as usual we need to measure the level of the consensus on them > > all thoughts or comments are very well welcome and appreciated. > > > cheers > /Sal > > www.sloreto.com > > > _______________________________________________ > hybi mailing list > hybi@ietf.org > https://www.ietf.org/mailman/listinfo/hybi > >
- [hybi] Requirement: extensions and sub protocols Salvatore Loreto
- Re: [hybi] Requirement: extensions and sub protoc… KOMATSU Kensaku
- Re: [hybi] Requirement: extensions and sub protoc… Jamie Lokier
- Re: [hybi] Requirement: extensions and sub protoc… Jamie Lokier
- Re: [hybi] Requirement: extensions and sub protoc… KOMATSU Kensaku
- Re: [hybi] Requirement: extensions and sub protoc… Greg Wilkins
- Re: [hybi] Requirement: extensions and sub protoc… Salvatore Loreto
- Re: [hybi] Requirement: extensions and sub protoc… Greg Wilkins
- Re: [hybi] Requirement: extensions and sub protoc… Salvatore Loreto
- Re: [hybi] Requirement: extensions and sub protoc… Jamie Lokier
- Re: [hybi] Requirement: extensions and sub protoc… Jamie Lokier
- Re: [hybi] Requirement: extensions and sub protoc… Jamie Lokier
- Re: [hybi] Requirement: extensions and sub protoc… KOMATSU Kensaku