Re: [hybi] hybi Digest, Vol 8, Issue 41

Ted Goddard <ted.goddard@icesoft.com> Fri, 30 October 2009 22:41 UTC

Return-Path: <ted.goddard@icesoft.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 9DAAD3A68B1 for <hybi@core3.amsl.com>; Fri, 30 Oct 2009 15:41:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.74
X-Spam-Level:
X-Spam-Status: No, score=-0.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74]
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 AGoDKlDFmbw1 for <hybi@core3.amsl.com>; Fri, 30 Oct 2009 15:41:53 -0700 (PDT)
Received: from mail.icesoft.com (mail.icesoft.com [64.40.113.99]) by core3.amsl.com (Postfix) with ESMTP id 3408A3A6843 for <hybi@ietf.org>; Fri, 30 Oct 2009 15:41:53 -0700 (PDT)
Received: from tetra.icesoft.domain ([64.141.118.170]) (authenticated user tgoddard@icesoft.com) by mail.icesoft.com (Kerio MailServer 6.7.0) (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)); Fri, 30 Oct 2009 15:42:07 -0700
Content-Type: text/plain; charset="us-ascii"; format="flowed"; delsp="yes"
Mime-Version: 1.0 (Apple Message framework v1076)
From: Ted Goddard <ted.goddard@icesoft.com>
In-Reply-To: <91a5e3ea0910301458q465e5778kb46bcaedc65595a6@mail.gmail.com>
Date: Fri, 30 Oct 2009 16:42:07 -0600
Content-Transfer-Encoding: 7bit
Message-Id: <52F2D33D-DEEF-48CE-B510-1FD322ACBBDB@icesoft.com>
References: <mailman.3820.1256908248.4669.hybi@ietf.org> <91a5e3ea0910301458q465e5778kb46bcaedc65595a6@mail.gmail.com>
To: hybi@ietf.org, Jason Duell <jduell.mcbugs@gmail.com>
X-Mailer: Apple Mail (2.1076)
Subject: Re: [hybi] hybi Digest, Vol 8, Issue 41
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: Fri, 30 Oct 2009 22:41:54 -0000

Without multiplexing, I expect we will see each Ajax component
in each page opening its own socket, and multiple pages open
to the same server is very common (users often forget that
they already have a window open in their browser) so a hundred
connections to a single server would not be unexpected.

It's easy to ignore this at the moment because we are so accustomed
to the multiplexing in HTTP 1.1 (think back to the network overhead
of HTTP 1.0).

Regards,
Ted.

On 2009-10-30, at 3:58 PM, Jason Duell wrote:

>> multiplexing protocol implemented in browser/server (not in  
>> application).
>
> What's the use case here?  If a browser has two pages open that each
> want to connect to the same server?  How likely is that?