Re: [hybi] [whatwg] Web sockets and existing HTTP stacks

Greg Wilkins <gregw@webtide.com> Sat, 19 December 2009 01:13 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 CFB493A65A6 for <hybi@core3.amsl.com>; Fri, 18 Dec 2009 17:13:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.953
X-Spam-Level:
X-Spam-Status: No, score=-1.953 tagged_above=-999 required=5 tests=[AWL=-0.646, BAYES_00=-2.599, MISSING_HEADERS=1.292]
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 5YDr+3uAZOpw for <hybi@core3.amsl.com>; Fri, 18 Dec 2009 17:13:02 -0800 (PST)
Received: from mail-yx0-f192.google.com (mail-yx0-f192.google.com [209.85.210.192]) by core3.amsl.com (Postfix) with ESMTP id 17FB43A68FF for <hybi@ietf.org>; Fri, 18 Dec 2009 17:13:01 -0800 (PST)
Received: by yxe30 with SMTP id 30so4134626yxe.29 for <hybi@ietf.org>; Fri, 18 Dec 2009 17:12:44 -0800 (PST)
Received: by 10.100.40.7 with SMTP id n7mr7384223ann.170.1261185164225; Fri, 18 Dec 2009 17:12:44 -0800 (PST)
Received: from ?10.10.1.11? (60-242-119-126.tpgi.com.au [60.242.119.126]) by mx.google.com with ESMTPS id 13sm1766034gxk.13.2009.12.18.17.12.41 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 18 Dec 2009 17:12:43 -0800 (PST)
Message-ID: <4B2C287E.1030006@webtide.com>
Date: Sat, 19 Dec 2009 12:12:30 +1100
From: Greg Wilkins <gregw@webtide.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
References: <557ae280911171402v7546e5e7n93a1e57f87dc10e5@mail.gmail.com> <557ae280911200711i5493e654k67c1f5f07336bfb9@mail.gmail.com> <Pine.LNX.4.62.0912032347360.15540@hixie.dreamhostps.com> <4B2C1D52.9020505@webtide.com> <5c902b9e0912181640n497169cdrfa71f9a2908e6ef3@mail.gmail.com> <20091219005442.GA10949@shareable.org>
In-Reply-To: <20091219005442.GA10949@shareable.org>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: whatwg@whatwg.org, hybi@ietf.org
Subject: Re: [hybi] [whatwg] Web sockets and existing HTTP stacks
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: Sat, 19 Dec 2009 01:13:03 -0000

Jamie Lokier wrote:
> For protocols which don't look like HTTP, you mainly do it because
> sometimes TCP port 80 is the only available outgoing port in
> firewalled environments.  Ironically, there is often an intercepting
> proxy in such environments, so it won't actually work.

In countries with repressive regimes that are against free
speech ( eg. Australia), there will always be a proxy on port
80 making sure that you don't read about religions (eg falun gong)
that offend our major trading partners (eg china) etc.

So websocket is specified to not work at all in Australia.
Of course it probably will work - but not because it is
specified to do so, but because the proxies just happen
to be implemented in certain ways.   Happen stance is
not a great basis for a protocol.

cheers