Re: [hybi] Extensibility mechanisms?

Scott Ferguson <ferg@caucho.com> Thu, 22 July 2010 02:14 UTC

Return-Path: <ferg@caucho.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 EC88C3A69B6 for <hybi@core3.amsl.com>; Wed, 21 Jul 2010 19:14:13 -0700 (PDT)
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 0ydIT9eMm7Qg for <hybi@core3.amsl.com>; Wed, 21 Jul 2010 19:14:13 -0700 (PDT)
Received: from smtp115.biz.mail.re2.yahoo.com (smtp115.biz.mail.re2.yahoo.com [66.196.116.35]) by core3.amsl.com (Postfix) with SMTP id DA4863A698E for <hybi@ietf.org>; Wed, 21 Jul 2010 19:14:12 -0700 (PDT)
Received: (qmail 52234 invoked from network); 22 Jul 2010 02:14:26 -0000
Received: from [192.168.1.11] (ferg@66.92.8.203 with plain) by smtp115.biz.mail.re2.yahoo.com with SMTP; 21 Jul 2010 19:14:26 -0700 PDT
X-Yahoo-SMTP: L1_TBRiswBB5.MuzAo8Yf89wczFo0A2C
X-YMail-OSG: g9g1fIIVM1nLsq5eUgPCqVZCCENCh.3.TiPgu_awwy.eePS w8D470H9azuBzhqPGQebaNrjvJy6JjthfXy2X5FHKz_8NhmRZkQH2h0ILvgA KH.xRg6nPWocW_ar1RN1_GoYGMb61J5FIG9TeS2IoKvtT6rEHFiZvaw9E9CK 9cnswCICFRKvGP6n3rqN5VLXXKZdAgK_b_eQ4bvF.AIXQEke9FBIhQnMM0AA rGcBSds72SVZR8M2zEhYLGZ9PJyY39boV7YFZD_OZqBvHhQw6I4R0ce852jE PVEtwyoVjQ.4wd.JYxUmB04kJPiz8KSl6i2Qs3cfVsCGmNPDgA9ToUh8K1IY pR_HLaA4eCVEZIr.mYc1vUrATWUIZpwenNrW5mYNYsB10rRxeaCgFBvy9tJ6 mRbYSR1ErylErERsp9g--
X-Yahoo-Newman-Property: ymail-3
Message-ID: <4C47A97C.5090500@caucho.com>
Date: Wed, 21 Jul 2010 19:14:20 -0700
From: Scott Ferguson <ferg@caucho.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: Maciej Stachowiak <mjs@apple.com>
References: <h2w5c902b9e1004152345j992b815bz5f8d38f06a19181a@mail.gmail.com> <4BCAB2C1.2000404@webtide.com> <B9DC25B0-CD21-44E7-BD9B-06D0C9440933@apple.com> <4BCB7829.9010204@caucho.com> <Pine.LNX.4.64.1004182349240.751@ps20323.dreamhostps.com> <4BCC0A07.9030003@gmx.de> <Pine.LNX.4.64.1004190753510.23507@ps20323.dreamhostps.com> <4BCC111C.90707@gmx.de> <Pine.LNX.4.64.1004190837570.23507@ps20323.dreamhostps.com> <4BCC204D.30004@gmx.de> <z2gad99d8ce1004190822ne4dd36b6v54d63efcc448e840@mail.gmail.com> <Pine.LNX.4.64.1007202204270.7242@ps20323.dreamhostps.com> <AANLkTikkfdlUxQ0MGNvVQKa5gfovkGHWdCgyN9juKSQJ@mail.gmail.com> <4C462F9E.9030207@caucho.com> <Pine.LNX.4.64.1007212153110.7242@ps20323.dreamhostps.com> <AANLkTiku76oSucTNDFdwgsFBNFa_cCpC-YktTnMfX47-@mail.gmail.com> <4C479130.4020500@caucho.com> <B6EA60FA-53BB-49AD-82B4-D1E7B460C297@apple.com> <4C479F8D.8030601@caucho.com> <D1F89752-F5D4-4C02-B78D-DDD7FFF91CB1@apple.com>
In-Reply-To: <D1F89752-F5D4-4C02-B78D-DDD7FFF91CB1@apple.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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: Thu, 22 Jul 2010 02:14:14 -0000

Maciej Stachowiak wrote:
> You said it solved all the requirements, so I was interested to find out if this was really so. It looks like that is not the case with your current draft, although it does have some nice properties.
>   
You're right about that. I do apologize for the overreach.

The missing binary/framing/control/stream requirements are the issue I'm 
worried about, and wanted to show it was possible to satisfy with a 
simple protocol, creating a more formal writeup of the related framing 
discussions on the list. The handshake was tacked on only for completeness.

Basically a proof of existence, because those requirements were being 
written off as too difficult. (And because no one else was stepping up 
to do it and they're trivial.)

Also, some of the related discussions were not grounded in an actual 
protocol.  For example, Jamie Lockier's ideas to reduce round trips 
sound like they're impossible to reconcile with the cross-site scripting 
issues. In the concrete proposal, both you and Mike saw problems 
immediately, but I don't recall his ideas being dismissed in that 
thread. (Although it was a few months ago.)

-- Scott
> Regards,
> Maciej
>
>
>
>
>