Re: [hybi] Apples and Orangutans

Maciej Stachowiak <mjs@apple.com> Sun, 12 April 2009 22:03 UTC

Return-Path: <mjs@apple.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 7F0A13A6C3F for <hybi@core3.amsl.com>; Sun, 12 Apr 2009 15:03:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 BtkoyhboNA8v for <hybi@core3.amsl.com>; Sun, 12 Apr 2009 15:03:37 -0700 (PDT)
Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by core3.amsl.com (Postfix) with ESMTP id D2EE53A6C0A for <hybi@ietf.org>; Sun, 12 Apr 2009 15:03:37 -0700 (PDT)
Received: from relay13.apple.com (relay13.apple.com [17.128.113.29]) by mail-out4.apple.com (Postfix) with ESMTP id 30B6F5EC5E28 for <hybi@ietf.org>; Sun, 12 Apr 2009 15:04:48 -0700 (PDT)
Received: from relay13.apple.com (unknown [127.0.0.1]) by relay13.apple.com (Symantec Brightmail Gateway) with ESMTP id 1C75B28085 for <hybi@ietf.org>; Sun, 12 Apr 2009 15:04:48 -0700 (PDT)
X-AuditID: 1180711d-a96f6bb000000259-63-49e2657f2e6d
Received: from gertie.apple.com (gertie.apple.com [17.151.62.15]) by relay13.apple.com (Apple SCV relay) with ESMTP id DEF3F2807D for <hybi@ietf.org>; Sun, 12 Apr 2009 15:04:47 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Received: from [10.0.1.7] (c-69-181-43-20.hsd1.ca.comcast.net [69.181.43.20]) by gertie.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0KI000HY9DBZ4L20@gertie.apple.com> for hybi@ietf.org; Sun, 12 Apr 2009 15:04:47 -0700 (PDT)
Message-id: <A3699591-148C-4795-967A-6CDE23FE75F0@apple.com>
From: Maciej Stachowiak <mjs@apple.com>
To: Rob Sayre <rsayre@mozilla.com>
In-reply-to: <49DEF171.4080506@mozilla.com>
Date: Sun, 12 Apr 2009 15:04:46 -0700
References: <49DEF171.4080506@mozilla.com>
X-Mailer: Apple Mail (2.930.3)
X-Brightmail-Tracker: AAAAAA==
Cc: hybi@ietf.org
Subject: Re: [hybi] Apples and Orangutans
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, 12 Apr 2009 22:03:38 -0000

On Apr 10, 2009, at 12:12 AM, Rob Sayre wrote:

> Ian Hickson wrote:
>> Personally I am interested in "Minimal, Event", but I don't see any
>> reason why we wouldn't also have the other models.
>
> I am interested in "Minimal, Event" as well.

I like Minimal/Event too, although I am starting to think the  
WebSocket protocol may be a bit too minimal. I think adding an  
optional type field to the packet or to the initial negotiation would  
help independently developed client and server code coordinate, much  
in the way MIME types help HTTP clients and servers without the  
necessity to define every possible type up front or to couple a single  
client to a single server. Ethernet and IP include a protocol number  
in the packet, TCP includes a port number (associated with protocols  
by convention), and HTTP as mentioned has a Content-Type. Perhaps  
WebSocket could make use of the HTTP Content-Type to identify the type  
of WebSocket service being connected to, or else there could be a per- 
packet identifier, which would be leaning towards the "Message, Event"  
model.

Regards,
Maciej