Re: [hybi] Intermediaries (was: CML)

Brian <theturtle32@gmail.com> Mon, 23 August 2010 07:37 UTC

Return-Path: <theturtle32@gmail.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 0A5213A698B for <hybi@core3.amsl.com>; Mon, 23 Aug 2010 00:37:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 e82UKKObGdI7 for <hybi@core3.amsl.com>; Mon, 23 Aug 2010 00:37:27 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id E80A73A67CC for <hybi@ietf.org>; Mon, 23 Aug 2010 00:37:26 -0700 (PDT)
Received: by gwb20 with SMTP id 20so2337867gwb.31 for <hybi@ietf.org>; Mon, 23 Aug 2010 00:38:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=jblukaVR1C9M1t7kMbkkCsc/Tih54KCT184T6XvhuHg=; b=hiz0Ln7IsPYSP7hx6IC239IyJHGuyHDCnQfP3VQKQvHEw/qn6L0XuriFmX5JYGrY8G /r+2gYlOv3zIZgeJ3onREpr9EdzX/H9qFqxoWbeezBgtyDZHi2n5MRzjmjzWWWm+YRLj 30Kv93cnogCioxH4pJT/CbocOqi4uJkWClVBo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=HesafVK76xSm6nBqpI4m1O1Sjh7R+HXTUFFvBgWCRBhP+gDXwDng2dR91QiZUgGuhY UXw+yTS3jfThNBLRb2fj8ApJpOdYwgCkx33fa4y4mVnWRKL6nI00US7Hv8Hd+LbcCKss sfIS3qmkBsnnXfltIgc22VGCDQJUN5vGlfaSo=
MIME-Version: 1.0
Received: by 10.101.204.37 with SMTP id g37mr4834848anq.253.1282549080281; Mon, 23 Aug 2010 00:38:00 -0700 (PDT)
Received: by 10.231.158.82 with HTTP; Mon, 23 Aug 2010 00:38:00 -0700 (PDT)
In-Reply-To: <AANLkTin9CMobfnDDZzZ=1QFLh1cDN8Rb8tp5vrxJ7if2@mail.gmail.com>
References: <8B0A9FCBB9832F43971E38010638454F03EF2669F2@SISPE7MB1.commscope.com> <AANLkTi=G-gZ1+7uoYE=fhiKFUXoziWacx5_k-HfxC-0z@mail.gmail.com> <8B0A9FCBB9832F43971E38010638454F03EF266A07@SISPE7MB1.commscope.com> <AANLkTimTBLvHXTGciDM4ef1hNXPHn7cjR-kxbd8pBq3+@mail.gmail.com> <8B0A9FCBB9832F43971E38010638454F03EF266A27@SISPE7MB1.commscope.com> <AANLkTik+ayksyTdspXRfwZQ-dUeqxsut7PR10r4uo7AM@mail.gmail.com> <AANLkTin9CMobfnDDZzZ=1QFLh1cDN8Rb8tp5vrxJ7if2@mail.gmail.com>
Date: Mon, 23 Aug 2010 00:38:00 -0700
Message-ID: <AANLkTikobG9BEv4Jx8xgak=1PqKSr-UEzjcV3rJXVsmD@mail.gmail.com>
From: Brian <theturtle32@gmail.com>
To: Hybi <hybi@ietf.org>
Content-Type: multipart/alternative; boundary="0016e68e7f665653f1048e78ba3d"
Subject: Re: [hybi] Intermediaries (was: CML)
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: Mon, 23 Aug 2010 07:37:28 -0000

>
> It's a non-trivial problem.  These all sound nice, but the difference
>> between theory and practice here is fairly large.
>>
>> I'll give an example: how would you, as an intermediary, decide to
>> multiplex if you had an open WS stream to ws://example.com/a and someone
>> requested a stream to ws://example.com/b ?
>>
>
>
In my infrastructure that I'm working on building, I'm using HAProxy with
layer-7 inspection specifically to forward requests for different paths to
different physical servers.  I specifically -don't- want multiple paths at
the same hostname to be muxed on the same connection.  If you want two
different endpoints, open two distinct TCP connections and be done with it.
 If you want a single stream, design your server and subprotocol to
specifically handle all the use cases.

Brian