Re: [hybi] [Uri-review] ws: and wss: schemes

Greg Wilkins <gregw@webtide.com> Wed, 12 August 2009 00:02 UTC

Return-Path: <gregw@webtide.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 449BA3A6ABD; Tue, 11 Aug 2009 17:02:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.145
X-Spam-Level:
X-Spam-Status: No, score=-2.145 tagged_above=-999 required=5 tests=[AWL=0.454, 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 Juo+OWSJCUzm; Tue, 11 Aug 2009 17:02:44 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.234]) by core3.amsl.com (Postfix) with ESMTP id 7B1493A6A74; Tue, 11 Aug 2009 17:02:44 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id f9so1157797rvb.49 for <multiple recipients>; Tue, 11 Aug 2009 17:00:06 -0700 (PDT)
Received: by 10.140.203.8 with SMTP id a8mr412338rvg.83.1250035206540; Tue, 11 Aug 2009 17:00:06 -0700 (PDT)
Received: from ?10.10.1.11? (60-242-119-126.tpgi.com.au [60.242.119.126]) by mx.google.com with ESMTPS id l31sm6143207rvb.34.2009.08.11.17.00.03 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 11 Aug 2009 17:00:05 -0700 (PDT)
Message-ID: <4A8205F3.8040509@webtide.com>
Date: Wed, 12 Aug 2009 09:59:47 +1000
From: Greg Wilkins <gregw@webtide.com>
User-Agent: Thunderbird 2.0.0.22 (X11/20090608)
MIME-Version: 1.0
To: David Booth <david@dbooth.org>
References: <Pine.LNX.4.62.0908070531430.28566@hixie.dreamhostps.com> <1249651007.25446.8934.camel@dbooth-laptop> <0B450D619CC0486E8BD51C31FBA214AD@POCZTOWIEC> <1250025544.3990.1565.camel@dbooth-laptop>
In-Reply-To: <1250025544.3990.1565.camel@dbooth-laptop>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: Kristof Zelechovski <giecrilj@stegny.2a.pl>, uri-review@ietf.org, hybi@ietf.org, uri@w3.org
Subject: Re: [hybi] [Uri-review] ws: and wss: schemes
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: Wed, 12 Aug 2009 00:02:45 -0000

David Booth wrote:
> I respectfully disagree.  I think it is a virtual certainty that if the
> WSS protocol is useful, it will be used in ways far beyond its original
> intent.  I don't think it would be wise to artificially constrain the
> applicability of a new protocol by claiming that casual users are not
> 'legitimate'.


And this is EXACTLY where I have a big problem with the process to date.

The ws protocol has been designed in respect to a single proposed
javascript API to run within a browser.

There are many many uses for bidirectional web which go beyond
that simple restricted example.

I really believe that we should pause and consider the big picture.

It should be the IETF's remit to design a bidirectional protocol
for the web that is usable by a wide range of possible uses.

The W3C's websocket API should be just one consumer of that
protocol.

I really think that the hybi effort needs to be elevated to a
working group to progress this.

cheers