Re: [hybi] Multiple connections serialization and proxies

"Thomson, Martin" <Martin.Thomson@andrew.com> Thu, 22 April 2010 23:17 UTC

Return-Path: <Martin.Thomson@andrew.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 A87793A6783 for <hybi@core3.amsl.com>; Thu, 22 Apr 2010 16:17:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.956
X-Spam-Level:
X-Spam-Status: No, score=-1.956 tagged_above=-999 required=5 tests=[AWL=0.643, 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 JRm1VlCktw1o for <hybi@core3.amsl.com>; Thu, 22 Apr 2010 16:17:42 -0700 (PDT)
Received: from csmailgw2.commscope.com (csmailgw2.commscope.com [198.135.207.242]) by core3.amsl.com (Postfix) with ESMTP id 842573A6908 for <hybi@ietf.org>; Thu, 22 Apr 2010 16:17:39 -0700 (PDT)
Received: from [10.86.20.103] ([10.86.20.103]:8299 "EHLO ACDCE7HC2.commscope.com") by csmailgw2.commscope.com with ESMTP id S58103Ab0DVXR3 (ORCPT <rfc822; hybi@ietf.org>); Thu, 22 Apr 2010 18:17:29 -0500
Received: from SISPE7HC1.commscope.com (10.97.4.12) by ACDCE7HC2.commscope.com (10.86.20.103) with Microsoft SMTP Server (TLS) id 8.1.436.0; Thu, 22 Apr 2010 18:17:29 -0500
Received: from SISPE7MB1.commscope.com ([fe80::9d82:a492:85e3:a293]) by SISPE7HC1.commscope.com ([fe80::8a9:4724:f6bb:3cdf%10]) with mapi; Fri, 23 Apr 2010 07:17:25 +0800
From: "Thomson, Martin" <Martin.Thomson@andrew.com>
To: Jamie Lokier <jamie@shareable.org>
Date: Fri, 23 Apr 2010 07:18:53 +0800
Thread-Topic: [hybi] Multiple connections serialization and proxies
Thread-Index: AcricO/dtwQhofqUTQyq4eAOqX48PgAAH8WA
Message-ID: <8B0A9FCBB9832F43971E38010638454F03E7D06E06@SISPE7MB1.commscope.com>
References: <4BCF4932.8040303@gmail.com> <4BD09A2C.6060506@gmail.com> <x2n557ae281004221224i2a9a46c0k6f6f684c94de255c@mail.gmail.com> <8B0A9FCBB9832F43971E38010638454F03E7D06DF7@SISPE7MB1.commscope.com> <20100422225448.GG13951@shareable.org> <8B0A9FCBB9832F43971E38010638454F03E7D06E00@SISPE7MB1.commscope.com> <20100422230957.GI13951@shareable.org>
In-Reply-To: <20100422230957.GI13951@shareable.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-BCN: Meridius 1000 Version 3.4 on csmailgw2.commscope.com
X-BCN-Sender: Martin.Thomson@andrew.com
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] Multiple connections serialization 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: Thu, 22 Apr 2010 23:17:43 -0000

> You did specifically say it will be a problem when something reuses a
> connection or when a proxy multiplexes.  Clearly -if- those things are
> ever done, then just do them properly.

There is currently no mechanism described that would allow either party (browser or server) to identify virtual connections.

Thus, there is no way to do this "properly".
 
> Did I misunderstand and you meant something else?
> 
> > But I was talking about draft-hixie-thewebsocketprotocol-75.
> 
> No, you referred to concerns about connections being reused by two
> different apps, and about proxies multiplexing - neither of which
> appear in that document.

I was talking about the concrete proposals that exist (even if Greg's isn't on the ietf servers yet), and I'm sorry if there was an implication to the contrary.

To be honest, all this theoretical discussion, while occasionally a pleasant distraction, doesn't contribute much to progress.  I'd really like to see some concrete proposals.
 
> Either that or it's been radically changed since I read an earlier
> version

No, it hasn't.