IETF Logo Mail Archive

Re: [hybi] #1: HTTP Compliance

Greg Wilkins <gregw@webtide.com> Wed, 21 July 2010 23:09 UTC

Return-Path: <gregw@webtide.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 8F0EC3A6809 for <hybi@core3.amsl.com>; Wed, 21 Jul 2010 16:09:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.724
X-Spam-Level:
X-Spam-Status: No, score=-1.724 tagged_above=-999 required=5 tests=[AWL=0.252, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 EEd4owNI7VEa for <hybi@core3.amsl.com>; Wed, 21 Jul 2010 16:09:29 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 738233A6857 for <hybi@ietf.org>; Wed, 21 Jul 2010 16:09:29 -0700 (PDT)
Received: by fxm1 with SMTP id 1so4344178fxm.31 for <hybi@ietf.org>; Wed, 21 Jul 2010 16:09:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.86.59.12 with SMTP id h12mr939146fga.67.1279753785280; Wed, 21 Jul 2010 16:09:45 -0700 (PDT)
Received: by 10.223.112.129 with HTTP; Wed, 21 Jul 2010 16:09:45 -0700 (PDT)
In-Reply-To: <AANLkTingZLsWoejLWbEbXGy_9mBo4eBc_Kv0wW9_Q0Xr@mail.gmail.com>
References: <068.d07026741c6694cd80652d2a7d34f236@tools.ietf.org> <Pine.LNX.4.64.1005170918310.25609@ps20323.dreamhostps.com> <4BF11920.2080307@webtide.com> <Pine.LNX.4.64.1005171039050.25609@ps20323.dreamhostps.com> <4BF12FF1.2020101@webtide.com> <15307.1274106895.116423@Sputnik> <Pine.LNX.4.64.1005172259030.22838@ps20323.dreamhostps.com> <20100518003753.GP20356@shareable.org> <Pine.LNX.4.64.1005180229430.22838@ps20323.dreamhostps.com> <20100518121245.GR20356@shareable.org> <AANLkTiniCjBwm5T59as8jByM5xDhPMrea-GqZFpWPAVS@mail.gmail.com> <Pine.LNX.4.64.1005182105360.22838@ps20323.dreamhostps.com> <AANLkTingZLsWoejLWbEbXGy_9mBo4eBc_Kv0wW9_Q0Xr@mail.gmail.com>
Date: Thu, 22 Jul 2010 09:09:45 +1000
Message-ID: <AANLkTild4QZdIO56pvt7vPAC2LFb59cHy7QUsEWauzK4@mail.gmail.com>
From: Greg Wilkins <gregw@webtide.com>
To: John Tamplin <jat@google.com>
Content-Type: multipart/alternative; boundary="000e0cd2983ac58b1d048bede5c5"
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] #1: HTTP Compliance
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, 21 Jul 2010 23:09:30 -0000

On 22 July 2010 00:27, John Tamplin <jat@google.com> wrote:

>
> I'm not sold on connection reuse
>

Just to clearly (re)state a good use-case for connection reuse.

Currently the WS handshake can only be rejected by closing the connection
and discarding any potential HTTP response.  Thus a webapp that wishes to
fall back to a non-ws transport will have to establish a new connection,
maybe negotiate TLS, then handshake the new transport.   Thus there will be
an extra 2 or 3 round trips to establish the fall-back transport.

This is already a problem for cometd-2, as it will try WS and then fallback
to long polling.  I can visibly tell when establishing a chat room if I have
the WS transport enabled  in the client or not, because I can see the extra
delays as WS is tried and fails.

This will be a barrier to frameworks like cometd-2 including WS in their
transport negotiations.

v2.23.0 | Report a Bug | By Email