Re: [hybi] Moving to a CONNECT-based handshake

Jamie Lokier <jamie@shareable.org> Wed, 01 December 2010 09:52 UTC

Return-Path: <jamie@shareable.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 3A58128C101 for <hybi@core3.amsl.com>; Wed, 1 Dec 2010 01:52:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 tniIXpf5Skeh for <hybi@core3.amsl.com>; Wed, 1 Dec 2010 01:52:12 -0800 (PST)
Received: from mail2.shareable.org (mail2.shareable.org [80.68.89.115]) by core3.amsl.com (Postfix) with ESMTP id 2BA703A69DA for <hybi@ietf.org>; Wed, 1 Dec 2010 01:52:12 -0800 (PST)
Received: from jamie by mail2.shareable.org with local (Exim 4.63) (envelope-from <jamie@shareable.org>) id 1PNjNK-0002MD-29; Wed, 01 Dec 2010 09:53:22 +0000
Date: Wed, 01 Dec 2010 09:53:22 +0000
From: Jamie Lokier <jamie@shareable.org>
To: John Tamplin <jat@google.com>
Message-ID: <20101201095321.GH22787@shareable.org>
References: <op.vmzqkhszidj3kv@simon-pieterss-macbook.local> <4CF52558.9010100@gmx.de> <4CF529FF.9080708@opera.com> <BB31C4AB95A70042A256109D4619912605790150@XCH117CNC.rim.net> <AANLkTimzTvtho0m9HZSe6exgSwZxbCnxtmeJd2-G0aSK@mail.gmail.com> <BB31C4AB95A70042A256109D4619912605790178@XCH117CNC.rim.net> <BB31C4AB95A70042A256109D4619912605790190@XCH117CNC.rim.net> <AANLkTimQJz22RtoVnB16C8Mi4C8=QKB946wSR9BRsP85@mail.gmail.com> <AANLkTi=BPFKVfj1CQQ4pk9-M_-9=ftQQPerfAFZtV8K7@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <AANLkTi=BPFKVfj1CQQ4pk9-M_-9=ftQQPerfAFZtV8K7@mail.gmail.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] Moving to a CONNECT-based handshake
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: Wed, 01 Dec 2010 09:52:13 -0000

John Tamplin wrote:
> 
>    Should we consider initially supporting only port 443?> 
>    The downsides would be:
[...]
>      * some CPU overhead (though Google publications have indicated this
>        is very low)

* Memory overhead.

It's not unreasonable to consider a large WebSocket server handling on
the order of a million persistent connections.

TLS adds considerably to the minimum memory required to maintain each
socket, if those sockets are set to the minimum buffer size (to save
memory) because they are mostly idle carrying occasional tiny
messages, and used just so the server can send a notification to the
client.

TLS also seems to rule out transparent multiplexing (done by proxies)
to aggregate connections and keepalives, though there is no consensus
in favour of that anyway (and I'm not sure it _really_ rules it out).

-- Jamie