Re: [hybi] Is there a traffic jam?

"Sylvain Hellegouarch" <sh@defuze.org> Wed, 15 April 2009 07:33 UTC

Return-Path: <sh@defuze.org>
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 E67363A6B37 for <hybi@core3.amsl.com>; Wed, 15 Apr 2009 00:33:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.235
X-Spam-Level:
X-Spam-Status: No, score=-2.235 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
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 OgDjgF8yUepF for <hybi@core3.amsl.com>; Wed, 15 Apr 2009 00:33:51 -0700 (PDT)
Received: from mail1.webfaction.com (mail1.webfaction.com [67.15.2.85]) by core3.amsl.com (Postfix) with ESMTP id 0504C3A67EE for <hybi@ietf.org>; Wed, 15 Apr 2009 00:33:50 -0700 (PDT)
Received: from mail1.webfaction.com (localhost.localdomain [127.0.0.1]) by mail1.webfaction.com (8.12.11.20060308/8.13.3) with ESMTP id n3F7Z2od031164; Wed, 15 Apr 2009 02:35:02 -0500
Received: (from apache@localhost) by mail1.webfaction.com (8.12.11.20060308/8.12.11/Submit) id n3F7Z2Ts031162; Wed, 15 Apr 2009 09:35:02 +0200
X-Authentication-Warning: mail1.webfaction.com: apache set sender to sh@defuze.org using -f
Received: from 193.253.216.132 (SquirrelMail authenticated user platom_sylvain) by mail1.webfaction.com with HTTP; Wed, 15 Apr 2009 09:35:02 +0200 (CEST)
Message-ID: <54156.193.253.216.132.1239780902.squirrel@mail1.webfaction.com>
In-Reply-To: <49E512E2.6000404@webtide.com>
References: <03BCE29D-7AA5-4128-9F61-446E0229479A@lindenlab.com> <E51D5B15BFDEFD448F90BDD17D41CFF105A0C476@AHQEX1.andrew.com> <Pine.LNX.4.62.0904140002360.10339@hixie.dreamhostps.com> <49E3D66C.5060002@webtide.com> <49E3D731.30305@mozilla.com> <79ea848f0904131727w5d4bc0d8kc9914d26080a01fc@mail.gmail.com> <49E3DB47.5060801@webtide.com> <49E428DD.3070803@defuze.org> <086D9C6DD2C9407D8D8CE0601FF0FD4A@mercury> <50044.193.253.216.132.1239692803.squirrel@mail1.webfaction.com> <3f5bf96b0904141136j6bc6e179w34af8ebb449b8d70@mail.gmail.com> <49E512E2.6000404@webtide.com>
Date: Wed, 15 Apr 2009 09:35:02 +0200
From: Sylvain Hellegouarch <sh@defuze.org>
To: Greg Wilkins <gregw@webtide.com>
User-Agent: SquirrelMail/1.4.8-6.el3
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: hybi@ietf.org
Subject: Re: [hybi] Is there a traffic jam?
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: sh@defuze.org
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: Wed, 15 Apr 2009 07:33:52 -0000

> Mike Dierken wrote:
>> I was thinking the applet would expose the 'web socket' API (or
>> equivalent) and the app would be built with JavaScript. This would be
>> a way to prototype an approach that created a sibling of
>> XMLHttpRequest, but meant for receiving unsolicited requests in a page
>> - something like XMLHttpServer (but without the XML part).
>
>
> Having access to TCP does not really help much.
>
> You still will not be able to tunnel through many firewalls
> and proxies without pretending to be HTTP.

But that's exactly the point, isn't it? Instead of reinventing the wheel
to go through firewalls and proxies, you reuse what's been defined,
refined and tested over decades of networking.

Corporations will always want at some point to control their traffic, they
have already administrators that know how to handle the basic TCP routing.
Here we are trying to defeat that but ultimately software will be upgraded
to filter WS anyway if required. You just add a layer of complexity to the
game. I fail to understand the value in that. Why not educating players in
the game to play fair? Port 80 is spoiled more and more and that means
it's more and more complex to perform proper security without basically
shutting down almost anything going through.

>
> Also as a client/application API, raw TCP is pretty
> difficult to code against.   What does an application do
> with 2 bytes of a 6-byte UTF-8 character.

It doesn't seem to have blocked the software industry so far. Libraries
handle those issues and offer higher level of abstraction for any given
protocol. JavaScript is short in those so far precisely due to the
constraints of not having access to raw TCP sockets I believe.

Why is the browser so different from anything else?

>
> I very much like websockets abstraction of utf-8 datagrams
> in the js/dom API.   This is very usable by applications
> and/or frameworks (I just don't think the transport should
> be skewed to support uncompressed UTF-8 datagrams without meta
> data.)

>From my perspective it's just one more layer of complexity.

- Sylvain
-- 
Sylvain Hellegouarch
http://www.defuze.org