Re: [hybi] New port and Tunneling?

Greg Wilkins <gregw@webtide.com> Mon, 16 August 2010 00:35 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 79A483A68F8 for <hybi@core3.amsl.com>; Sun, 15 Aug 2010 17:35:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.751
X-Spam-Level:
X-Spam-Status: No, score=-1.751 tagged_above=-999 required=5 tests=[AWL=0.226, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 1jFvei0nan-U for <hybi@core3.amsl.com>; Sun, 15 Aug 2010 17:35:57 -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 71C833A68F0 for <hybi@ietf.org>; Sun, 15 Aug 2010 17:35:57 -0700 (PDT)
Received: by fxm18 with SMTP id 18so3132189fxm.31 for <hybi@ietf.org>; Sun, 15 Aug 2010 17:36:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.104.15 with SMTP id m15mr4476925fao.103.1281918993032; Sun, 15 Aug 2010 17:36:33 -0700 (PDT)
Received: by 10.223.57.12 with HTTP; Sun, 15 Aug 2010 17:36:32 -0700 (PDT)
In-Reply-To: <52530df7491f03990cbfffd3eb49bcb6.squirrel@sm.webmail.pair.com>
References: <7ffabb591b2292c9b81abecfaec3cdb6.squirrel@sm.webmail.pair.com> <20100815210332.GH27614@1wt.eu> <a8358c0239c686dfd4753b55c6c34385.squirrel@sm.webmail.pair.com> <20100815221922.GJ27614@1wt.eu> <b13c89a75303a5d97edcb78926b385be.squirrel@sm.webmail.pair.com> <20100815234010.GM27614@1wt.eu> <52530df7491f03990cbfffd3eb49bcb6.squirrel@sm.webmail.pair.com>
Date: Mon, 16 Aug 2010 10:36:32 +1000
Message-ID: <AANLkTi==qsBWRDhxten+fV91bYiBhJ_vhSoqPNpsp3Pb@mail.gmail.com>
From: Greg Wilkins <gregw@webtide.com>
To: shelby@coolpage.com
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: hybi@ietf.org
Subject: Re: [hybi] New port and Tunneling?
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, 16 Aug 2010 00:35:58 -0000

On 16 August 2010 10:24, Shelby Moore <shelby@coolpage.com> wrote:
>> On Sun, Aug 15, 2010 at 07:03:05PM -0400, Shelby Moore wrote:
> We must have that fallback no matter what we do.  All options forward have
> failure cases.
>
>> If I had the choice, I'd rather go for
>> WS/TLS with a quick fail to WS/HTTP.
>
>
> WS/HTTP can fail at random times after that quick fail, you still need
> Comet/BOSH.

and Comet/BOSH can fail at random times.
All solutions need to handle the fact that the internet can fail silently.

I do not think it is possible to design a system that will always fast
fail, other than an explicit declaration by a participant that a
protocol is not supported.   It is impossible to design a handshake,
whose success will guarantee the delivery of a subsequent websocket
message .

The only real evidence of a protocol working is the protocol working.
The level of confidence in the protocol will be determined only by
mechanisms built into the protocol: messages, keep-alives, ping/pongs
and any extensions for acknowledgements etc.

There is no silver bullet.