Re: [hybi] Working over existing firewalls and proxies

Maciej Stachowiak <mjs@apple.com> Tue, 14 April 2009 23:00 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 9723A3A6AF6 for <hybi@core3.amsl.com>; Tue, 14 Apr 2009 16:00:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.999
X-Spam-Level:
X-Spam-Status: No, score=-105.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_22=0.6, 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 pvtceOUAhQr1 for <hybi@core3.amsl.com>; Tue, 14 Apr 2009 16:00:55 -0700 (PDT)
Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by core3.amsl.com (Postfix) with ESMTP id A8D8B3A677D for <hybi@ietf.org>; Tue, 14 Apr 2009 16:00:34 -0700 (PDT)
Received: from relay10.apple.com (relay10.apple.com [17.128.113.47]) by mail-out3.apple.com (Postfix) with ESMTP id B262B5C74CBA for <hybi@ietf.org>; Tue, 14 Apr 2009 16:01:46 -0700 (PDT)
Received: from relay10.apple.com (unknown [127.0.0.1]) by relay10.apple.com (Symantec Brightmail Gateway) with ESMTP id 8C0362806A for <hybi@ietf.org>; Tue, 14 Apr 2009 16:01:46 -0700 (PDT)
X-AuditID: 1180712f-aa16dbb0000012d3-a9-49e515da577c
Received: from et.apple.com (et.apple.com [17.151.62.12]) by relay10.apple.com (Apple SCV relay) with ESMTP id 744C728057 for <hybi@ietf.org>; Tue, 14 Apr 2009 16:01:46 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Received: from il0301a-dhcp77.apple.com (il0301a-dhcp77.apple.com [17.203.14.205]) by et.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0KI400FM45AY9W70@et.apple.com> for hybi@ietf.org; Tue, 14 Apr 2009 16:01:46 -0700 (PDT)
Message-id: <30F5867C-5081-422B-BF51-FE84EA6C686E@apple.com>
From: Maciej Stachowiak <mjs@apple.com>
To: Greg Wilkins <gregw@webtide.com>
In-reply-to: <49E51506.1020500@webtide.com>
Date: Tue, 14 Apr 2009 16:01:45 -0700
References: <49E3D363.8030803@mozilla.com> <49E3D937.5020009@webtide.com> <20090414153243.GD26621@shareable.org> <79ea848f0904141018j59659f21n82944f3723409991@mail.gmail.com> <49E51506.1020500@webtide.com>
X-Mailer: Apple Mail (2.930.3)
X-Brightmail-Tracker: AAAAAA==
Cc: hybi@ietf.org
Subject: Re: [hybi] Working over existing firewalls and proxies
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: Tue, 14 Apr 2009 23:00:56 -0000

On Apr 14, 2009, at 3:58 PM, Greg Wilkins wrote:

> Mario Balibrera wrote:
>> Currently, js.io <http://js.io> works that way with WebSocket. If  
>> there is a native browser implementation available (none yet,  
>> obviousy)
>
>
> I find it really strange that there are no browsers that currently
> implement Websocket.   It's been around for a while now and I've
> frequently asked if there is a browser that supports it - even
> a branch of one of the OS browsers.
>
> So far I've drawn a blank... and because the browsers are not
> implementing it, I've felt no great need to add it to my
> Jetty server.
>
> So there are some browser builders on this list - can any
> of them volunteer why there has been no experimentation with
> websocket?
>
> Anybody know why the websocket designers have not tested their
> proposal with an extension to firefox or similar?

We're pacing ourselves on adding new features. We can only add so much  
per release cycle, and WebSocket has been significantly redesigned  
fairly recently (from a state we would have considered unacceptable).  
However, I think most browser vendors / developers consider support  
for bidirectional communication a fairly high priority - certainly we  
are very interested in it for Safari and WebKit, and WebSocket seems  
like a good solution in this space.

Regards,
Maciej