IETF Logo Mail Archive

Re: [hybi] Multiplexing extension spec draft 03

John Tamplin <jat@google.com> Tue, 27 March 2012 14:16 UTC

Return-Path: <jat@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6603621F881D for <hybi@ietfa.amsl.com>; Tue, 27 Mar 2012 07:16:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.976
X-Spam-Level:
X-Spam-Status: No, score=-102.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k-4PaNtDF22N for <hybi@ietfa.amsl.com>; Tue, 27 Mar 2012 07:16:49 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9120521F8821 for <hybi@ietf.org>; Tue, 27 Mar 2012 07:16:48 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so3932931vbb.31 for <hybi@ietf.org>; Tue, 27 Mar 2012 07:16:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-system-of-record; bh=C8/+dyDP7mOdkwqsV9weH9RSUvV9J0+pvM4QFu5Fgw0=; b=iX7oXRWzrBL8GZlqJtqNg/szSuIjVxm/x+R+UxV73QZUQgD+d7YwgQ16PNzIcGejub W2uPDJzdaoALtVvbMFYAQbB8BZWu81Ywu3f6lkNpeiAZW1+gL6XKGRstM8LsQjuYvHOp P0uG2U1WMILkoNgYcbtDd3042FNuHqtRtPkno6hjC95cNLzzHxQWhgWWwDaH5fLKIxKD Fa0/O7g98v2hQjIVsg4WJplkodlZVn/rRe+il3fVGtxsUKTjTStXYyco2Bax0RaUxCxT DbpARZEn9LcNpJ+yfGuKjr0W1pfD+4BqdJrZ2Xejb60Gp6ukI4xxTRcxqgxlMmZn9D1D GruA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-system-of-record:x-gm-message-state; bh=C8/+dyDP7mOdkwqsV9weH9RSUvV9J0+pvM4QFu5Fgw0=; b=BQRjv9xMjcLlKfOxLyP0otbcfbpmuTOdWlAttKbkLm49CGncY1qhiFDGmyn1hNK64U Hb+HCASRIqCB6VOfFl6/dm/FU/kA+KohA5jt29XvMe9yuv/7NoIzwt7jFcaGBRYEBnfq K0NZbyUTekMWI/OWK2jl76q1TCxZWNEPWzObr1od6C+yhmLlLVJK66MUOPseL4MZTCej PuLucaf1+vjBKX+E3f1BsUeqHBb/eFHFrAhoXygfwKs6gwxbfNFghqRiixCZDkQJy4xR miT/8OflNQr8oxq+O1efKnJOk8lggmh5tXbM7nuK+lLwiumnGzNQQWG7FG1wfDNsNgA/ IM/g==
Received: by 10.220.228.200 with SMTP id jf8mr12091547vcb.0.1332857808060; Tue, 27 Mar 2012 07:16:48 -0700 (PDT)
Received: by 10.220.228.200 with SMTP id jf8mr12091534vcb.0.1332857807885; Tue, 27 Mar 2012 07:16:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.191.67 with HTTP; Tue, 27 Mar 2012 07:16:27 -0700 (PDT)
In-Reply-To: <002c01cd0c22$dd9e8fb0$98dbaf10$@noemax.com>
References: <CAH9hSJb1ewPO3EBgD78anD+=4XouToGR4X7C1wvWqonc2nYB6g@mail.gmail.com> <000301cd05dd$c8f9fc70$5aedf550$@noemax.com> <CAH9hSJYni6BboWdjkLX9xsguph7wJwjAmTUD1genFzT0ja5Wdw@mail.gmail.com> <003b01cd08d8$b1dd7050$159850f0$@noemax.com> <CAH9hSJYmL1ngaEJ1Th1kye2WKvJ4-zup1qbHCPLs+6MBOtS4Fg@mail.gmail.com> <001201cd0c06$3e9b3ab0$bbd1b010$@noemax.com> <CAH9hSJY1=KR-BrYUM-ACMVEVcb9+SMKH4fnoEfkyxu+6P4AwJA@mail.gmail.com> <002c01cd0c22$dd9e8fb0$98dbaf10$@noemax.com>
From: John Tamplin <jat@google.com>
Date: Tue, 27 Mar 2012 10:16:27 -0400
Message-ID: <CABLsOLDz0tuz+mdwJj3XhG++QM5HgnVS=R0WFj+01UL9+HujWg@mail.gmail.com>
To: Arman Djusupov <arman@noemax.com>
Content-Type: multipart/alternative; boundary="14dae9cdc0f92cd3d604bc3a24cd"
X-System-Of-Record: true
X-Gm-Message-State: ALoCoQm8crKkL0r2+oizVmQTLfNxAYvp7E9dICYoDY8yrIKxnGy8CfPEvF6/N8qaMrc2CMxrtQdRNG9PBihJstKPjurDPbs9FEiz0Fh/8TYkN3P/PvLYftSxdVQdaPGGxmaYtMaIW8mW
Cc: hybi@ietf.org
Subject: Re: [hybi] Multiplexing extension spec draft 03
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 27 Mar 2012 14:16:50 -0000

I really don't think exposing channels to JS is the proper thing to do.
 For one, that means that the application must be prepared to deal with
browsers which support and don't support MUX (and therefore don't even
provide that API), and connections that go through an intermediary that
doesn't support it.

Instead, I think applications that want multiple channels should just open
them as they do today.  If the browser and server negotiate MUX, then the
browser will aggregate those connections, and if not it will continue to
work.

-- 
John A. Tamplin
Software Engineer (GWT), Google

v2.23.0 | Report a Bug | By Email