Re: [hybi] WS port with BOSH-like fallback?

Jack Moffitt <jack@collecta.com> Wed, 01 December 2010 17:39 UTC

Return-Path: <metajack@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 C05543A6BED for <hybi@core3.amsl.com>; Wed, 1 Dec 2010 09:39:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level:
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
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 esVSmm-3OK8W for <hybi@core3.amsl.com>; Wed, 1 Dec 2010 09:39:47 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id 9394C3A6B48 for <hybi@ietf.org>; Wed, 1 Dec 2010 09:39:47 -0800 (PST)
Received: by bwz12 with SMTP id 12so6977182bwz.31 for <hybi@ietf.org>; Wed, 01 Dec 2010 09:41:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=s5aB5mtcts4Dn67rNSrd7ff8SCPBGxqsjJzhRwoEHSE=; b=VCJYc8gZ5HvBVDSF2raXC2ec9uaQlFTJnslGJwaZkEHUnXM4GUs5KMLVzeg8o1bIVo NbCa54Gg2W38V4iT8H4a/FlHMVkc2xR53P2mlrkLHb6G1Abw+ILDFU7Ft7VScpO76jqb rj5OmplnPJR0YA+uF/Glw8dr24cWl0kD2lNeo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=FAlpHFDhv5nLA/FeTlN2fp4bSJoKgT285dlCQjjYBIsqgYgWEDKz6vXh1e5C1IyUnE o+tR7fMnkU6NKsJra7K22sGAoK6YOxducfM8vM/2ybFwQGXZkwLwPBQ709uZP1gt7gjb Eie/+nMDC6WAZW386VlsapLka529g9er67MsA=
MIME-Version: 1.0
Received: by 10.204.118.7 with SMTP id t7mr1437408bkq.97.1291225260162; Wed, 01 Dec 2010 09:41:00 -0800 (PST)
Sender: metajack@gmail.com
Received: by 10.204.119.211 with HTTP; Wed, 1 Dec 2010 09:41:00 -0800 (PST)
In-Reply-To: <20101201152622.GL22787@shareable.org>
References: <AANLkTi=UpWdjqU0Lkh11wSGtHVDO71_CvjWJyH4mPyQi@mail.gmail.com> <4590EC7E9324CF43A2B37F81AFD6357007BB59B9@BANMLVEM07.e2k.ad.ge.com> <20101201105939.GK22787@shareable.org> <AANLkTinSRhb2N6_hfcXbfB5uM3pU+xubNN1kJcT5w3E4@mail.gmail.com> <20101201152622.GL22787@shareable.org>
Date: Wed, 01 Dec 2010 10:41:00 -0700
X-Google-Sender-Auth: VDGRaRJGpSezCi3-Xo1Tj9A6nEo
Message-ID: <AANLkTinjZzq6SMqH4TQXNnpn4mBp1XbP0rGnZ799r6+Z@mail.gmail.com>
From: Jack Moffitt <jack@collecta.com>
To: Jamie Lokier <jamie@shareable.org>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: Hybi <hybi@ietf.org>, "Alakkad, Achuth (GE Healthcare)" <Achuth.Alakkad@ge.com>, Greg Wilkins <gregw@intalio.com>
Subject: Re: [hybi] WS port with BOSH-like fallback?
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, 01 Dec 2010 17:39:49 -0000

> Has anyone tried measuring the connection success rate - and
> messages/packets/data/latencies - of "valid" HTTP port 80 techniques:
> such as single-connection bidirectional chunked POST, and various
> dual-connection pipelined-POST/GET (one upstream, one downstream)?

I don't have any scientific measurements, but I did run a chess
community of about 400k users, and we experienced close to 100%
connection success rate as far as I could tell.  This was using XMPP
BOSH, which on a client typically uses the same two sockets for the
life of the page, and exchanges full HTTP requests and responses
containing XML.  Compression is even used almost always from server to
client, but only on certain browsers in the opposite direction.

My anecdotal experience was that except in the very rare cases were
intermediares have forced timeouts on connection length, everything
worked without a hitch (modulo temporary network failure).  In the
cases where connections were forced closed after N seconds (where N <
60 or so), things still worked, but latency was terrible.

Our success rate for direct XMPP connections with the desktop client
was not as good, since many places block everything but port 80 and
443.  It was always our intention to have the desktop client fall back
to BOSH since BOSH seemed the most reliable.

jack.