Re: [hybi] Is there a traffic jam?

Mark Lentczner <markl@lindenlab.com> Thu, 16 April 2009 02:01 UTC

Return-Path: <markl@lindenlab.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 2D3EA3A6961 for <hybi@core3.amsl.com>; Wed, 15 Apr 2009 19:01:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.999
X-Spam-Level:
X-Spam-Status: No, score=-2.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
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 ntbzuJA77ZR8 for <hybi@core3.amsl.com>; Wed, 15 Apr 2009 19:01:15 -0700 (PDT)
Received: from tammy.lindenlab.com (tammy.lindenlab.com [64.154.223.128]) by core3.amsl.com (Postfix) with ESMTP id 548ED3A67FC for <hybi@ietf.org>; Wed, 15 Apr 2009 19:01:15 -0700 (PDT)
Received: from [192.168.1.192] (m208-18.dsl.rawbw.com [198.144.208.18]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tammy.lindenlab.com (Postfix) with ESMTP id 842D21414002 for <hybi@ietf.org>; Wed, 15 Apr 2009 19:02:27 -0700 (PDT)
Message-Id: <146BB157-60BF-4942-869B-18F7BA7474F7@lindenlab.com>
From: Mark Lentczner <markl@lindenlab.com>
To: hybi@ietf.org
In-Reply-To: <54156.193.253.216.132.1239780902.squirrel@mail1.webfaction.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
X-Priority: 3 (Normal)
Date: Wed, 15 Apr 2009 18:35:10 -0700
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> <54156.193.253.216.132.1239780902.squirrel@mail1.webfaction.com>
X-Mailer: Apple Mail (2.930.3)
Subject: Re: [hybi] Is there a traffic jam?
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, 16 Apr 2009 02:01:16 -0000

Wow - the only traffic jam seems to be in my in-box! My this mailing  
list has gotten popular!

I tend to agree with the arguments against a minimal protocol such as  
WebSockets:
+1: there's nothing wrong using existing libraries for things like  
HTTP, XML, UTF-8, etc...
+1: inexperienced programmers are going to code to an API like CGI,  
not write the whole server
+1: you can make a good, easy to use API even for a rich protocol: to  
wit: CGI
+1: if the protocol is too minimal, the commonly used stuff will be  
implemented up the stack, which means:
	a) it will be non-interoperable
and	b)the infrastructure will not be able to interact with it

Other things I noticed:
- HTTP over SCTP *does* seem interesting. It might be nice to separate  
out the channeling and asynchrony from the bi-directionality. Now if  
we could do that, and have a fall back for today (not much SCTP in  
stock OSes...)... that is an interesting direction...
- Tunneling through existing firewall and proxy constraints seems to  
keep rearing its head. This feels to me like a separate concern: We  
should design what we think is useful, expect that in a few years  
firewalls and proxies will adapt, *and* design a pure HTTP fallback  
that will allow us to "get on with it" today.

	- Mark

Mark Lentczner
Sr. Systems Architect
Technology Integration
Linden Lab

markl@lindenlab.com

Zero Linden
zero.linden@secondlife.com