Re: [hybi] Extensibility mechanisms?

Greg Wilkins <gregw@webtide.com> Mon, 19 April 2010 09:00 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 2AC193A659C for <hybi@core3.amsl.com>; Mon, 19 Apr 2010 02:00:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.59
X-Spam-Level:
X-Spam-Status: No, score=-0.59 tagged_above=-999 required=5 tests=[AWL=-0.405, BAYES_40=-0.185]
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 HAXJJoQZwm1n for <hybi@core3.amsl.com>; Mon, 19 Apr 2010 02:00:15 -0700 (PDT)
Received: from mail-bw0-f225.google.com (mail-bw0-f225.google.com [209.85.218.225]) by core3.amsl.com (Postfix) with ESMTP id 265F73A6900 for <hybi@ietf.org>; Mon, 19 Apr 2010 02:00:13 -0700 (PDT)
Received: by bwz25 with SMTP id 25so5213374bwz.28 for <hybi@ietf.org>; Mon, 19 Apr 2010 02:00:00 -0700 (PDT)
Received: by 10.204.82.230 with SMTP id c38mr4435631bkl.213.1271667600646; Mon, 19 Apr 2010 02:00:00 -0700 (PDT)
Received: from [192.168.0.100] (host116-234-static.43-88-b.business.telecomitalia.it [88.43.234.116]) by mx.google.com with ESMTPS id 16sm3035962bwz.13.2010.04.19.01.59.59 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 19 Apr 2010 01:59:59 -0700 (PDT)
Message-ID: <4BCC1B8D.6080307@webtide.com>
Date: Mon, 19 Apr 2010 10:59:57 +0200
From: Greg Wilkins <gregw@webtide.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: Hybi <hybi@ietf.org>
References: <h2w5c902b9e1004152345j992b815bz5f8d38f06a19181a@mail.gmail.com> <Pine.LNX.4.64.1004160701250.751@ps20323.dreamhostps.com> <4BC860FD.8080007@webtide.com> <Pine.LNX.4.64.1004161952530.751@ps20323.dreamhostps.com> <4BC96A0D.4080904@webtide.com> <Pine.LNX.4.64.1004180246380.751@ps20323.dreamhostps.com> <4BCC1339.5000602@it.aoyama.ac.jp>
In-Reply-To: <4BCC1339.5000602@it.aoyama.ac.jp>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Subject: Re: [hybi] Extensibility mechanisms?
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: Mon, 19 Apr 2010 09:00:16 -0000

Martin J. Dürst wrote:
> On 2010/04/18 11:55, Ian Hickson wrote:
>> On Sat, 17 Apr 2010, Greg Wilkins wrote:
>>>
>>> I'm sorry but despite your original aims, enabling amateur programmers
>>> to write protocols that avoid the need for vendor supplied
>>> infrastructure is not the prime reason this WG has come into existence.
>>
>> If that isn't a goal for this working group, then that's fine, but it
>> means I'm in the wrong group.
> 
> If what Greg wrote means that "you won't be able to deploy web sockets
> unless you pay one of these vendors a lot of money", then I clearly
> would disagree. But I sincerely hope that's not what Greg meant.

That is most definitely not what I meant.

As an open source developer, I've spent 15 years writing a
server that I give away for free.

What I meant is that I believe that the IETF is largely
compromised of individuals working for vendors who
have an interest in creating interoperable infrastructure.


The reason that we wish to create infrastructure, is not
part of some evil scheme to prevent application developers
from accessing the raw internet, and thus make millions
from selling our infrastructure products and services.
Rather it is because that we genuinely believe that
the best computer science solution to enable the
safe and efficient use of the network is to provide
some appropriate layer of infrastructure.


I don't oppose Ian's view of enabling application developers
to just crack open a socket and implement websockets because
I want to increase market share of Jetty.
I oppose it because it is a bad idea and will just result
in many insecure and bug ridden applications - not matter
how simple or trivial the protocol is.

regards