Re: [hybi] Extensibility mechanisms?

Roberto Peon <fenix@google.com> Sun, 18 April 2010 23:41 UTC

Return-Path: <fenix@google.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 CF75F3A68EA for <hybi@core3.amsl.com>; Sun, 18 Apr 2010 16:41:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.443
X-Spam-Level:
X-Spam-Status: No, score=-100.443 tagged_above=-999 required=5 tests=[AWL=-0.326, BAYES_20=-0.74, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
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 BeGNrJ-xAs4Z for <hybi@core3.amsl.com>; Sun, 18 Apr 2010 16:41:22 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.35]) by core3.amsl.com (Postfix) with ESMTP id 39C113A67A6 for <hybi@ietf.org>; Sun, 18 Apr 2010 16:41:22 -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 o3INfA6E023820 for <hybi@ietf.org>; Mon, 19 Apr 2010 01:41:10 +0200
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1271634070; bh=QcSHDqTHRIvF48h42/CU9/Cfaac=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=ODYfiv8/nAD2A0e79UGaYzs8i9qYr/WGMZHn/mkc2EUoWFs8oMNiuwbUzWTJn3x35 oenlp3jBJcGNbMUL3Oz5w==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:date:message-id:subject:from:to: cc:content-type:x-system-of-record; b=tKUixd72wF0rxMC+er9waAnVc+ValcMZCOGdoGImfItuhc62LFKuKDP3OmLUHIRe8 opv5S/8hN2Wcira+ZUdWg==
Received: from gxk23 (gxk23.prod.google.com [10.202.11.23]) by wpaz29.hot.corp.google.com with ESMTP id o3INf95c013372 for <hybi@ietf.org>; Sun, 18 Apr 2010 16:41:09 -0700
Received: by gxk23 with SMTP id 23so2523791gxk.15 for <hybi@ietf.org>; Sun, 18 Apr 2010 16:41:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.184.18 with HTTP; Sun, 18 Apr 2010 16:41:08 -0700 (PDT)
In-Reply-To: <4BCB7829.9010204@caucho.com>
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> <4BCAB2C1.2000404@webtide.com> <B9DC25B0-CD21-44E7-BD9B-06D0C9440933@apple.com> <4BCB7829.9010204@caucho.com>
Date: Sun, 18 Apr 2010 16:41:08 -0700
Received: by 10.150.194.2 with SMTP id r2mr5205021ybf.92.1271634068851; Sun, 18 Apr 2010 16:41:08 -0700 (PDT)
Message-ID: <h2iad99d8ce1004181641x16b5af5av194db2cefaca48ac@mail.gmail.com>
From: Roberto Peon <fenix@google.com>
To: Scott Ferguson <ferg@caucho.com>
Content-Type: multipart/alternative; boundary="000e0cdf1bd8f54d6304848b6054"
X-System-Of-Record: true
Cc: Hybi <hybi@ietf.org>
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: Sun, 18 Apr 2010 23:41:23 -0000

On Sun, Apr 18, 2010 at 2:22 PM, Scott Ferguson <ferg@caucho.com> wrote:

> Maciej Stachowiak wrote:
>
>> Why do I take this view? A large part of the Web's success has come from
>> the "long tail" of content that exists only because the underlying formats
>> and protocols make it easy to do simple things. This has led to the
>> explosive growth of the Web. At the same time, it's clearly important to
>> consider the needs of larger organizations as well. A solution that works
>> for Joe Hobbyist Programmer at home, but doesn't meet the needs of, say,
>> Facebook or Yahoo, is not a complete solution. Large sites are clearly a
>> critical part of the Web's success as well.
>>
> I think a little more precision is important here.
>
> The client and server APIs must be suitable for amateur programmers, and
> the wire protocol must support those simple APIs, but it's _not_ important
> that the wire protocol be implementable by someone who can't understand
> buffering, chunking or encoding. After all, HTTP/1.1 requires those
> capabilities.
>

> The "long tail" in HTTP is enabled by the server APIs: CGI, mod_xxx, PHP,
> Servlets, ASP, etc, and the client javascript API. It is indeed very
> important that the server-side and client-side APIs for WebSockets be usable
> by hobbyist programmers to do simple things.
>
> However, the "long tail" are not writing hobbyist HTTP client or server
> protocol implementations.
>
> In addition, WebSockets is intrinsically multithreaded, which makes the
> claim that it's aimed at amateur implementers bizarre. WebSockets requires
> threading/async handling on both ends, which is beyond the capabilities of
> these hypothetical amateur programmers who cannot encode a simple frame.
> Programmers who can implement a threaded/async server can handle the trivial
> framing we're discussing. If they can't handle the framing, the
> threading/async requirements are beyond them.
>
> That's not a license to create CORBA 2, but does mean it's reasonable to
> require a basic level of competence from implementers.
>


Thanks, Scott, this is exactly my view as well.
 -=R



>
> -- Scott
>
>
>> I think ultimately these two goals are not fundamentally at odds. It may
>> be more challenging to satisfy both sets of needs, but we have a lot of
>> smart people here so we should be able to figure it out.
>>
>>
>> Regards,
>> Maciej
>>
>>
>>
>>
>> _______________________________________________
>> hybi mailing list
>> hybi@ietf.org
>> https://www.ietf.org/mailman/listinfo/hybi
>>
>>
>>
>>
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>