IETF Logo Mail Archive

Re: [hybi] Ping/Pong body (was Re: TSV-Directorate review of draft-ietf-hybi-thewebsocketprotocol-07)

Pieter Hintjens <ph@imatix.com> Fri, 20 May 2011 10:08 UTC

Return-Path: <pieterh@gmail.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 D2712E0760 for <hybi@ietfa.amsl.com>; Fri, 20 May 2011 03:08:50 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WU+nI3oDi3TX for <hybi@ietfa.amsl.com>; Fri, 20 May 2011 03:08:50 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by ietfa.amsl.com (Postfix) with ESMTP id 0E1C0E0733 for <hybi@ietf.org>; Fri, 20 May 2011 03:08:49 -0700 (PDT)
Received: by qyk7 with SMTP id 7so2307811qyk.10 for <hybi@ietf.org>; Fri, 20 May 2011 03:08:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:from :date:x-google-sender-auth:message-id:subject:to:cc:content-type; bh=jnP2dIGCFSB1ekezoHhxO9NpHF6snJD3BZxxFe4xp40=; b=aboBcDeP154xCwpWbaRagok6LwRiQLXhGiOu418MtrFq+drswu1bfle9V3cuJZtuNm r5dxx3ABdflKuTVE3qtVlTCS4/FLxibLX4q1JEzuLu6r7jhuKZxsgn4wijHuPH8KAOru SLl3IjhXaAvk4BB9dqwLN/cNodTVDc0YucnSA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; b=lCpj1jkKngDnj6SP0RS5JjCBAE1qpMiDsEV4QEReJWrtYErmXnRyoYGnIbKiLJL3iK 1kGTlHPcZq250Sj63BWG+/2AM18v8lVRrIlx40IYD9mA6NqwC5+K2+XXK5k6LJYyQ24x /yV4w7R/Ym/Jmjbjnl3a/hrQ+8qgEj+QJjr14=
Received: by 10.229.106.83 with SMTP id w19mr3169189qco.186.1305886129178; Fri, 20 May 2011 03:08:49 -0700 (PDT)
MIME-Version: 1.0
Sender: pieterh@gmail.com
Received: by 10.229.181.202 with HTTP; Fri, 20 May 2011 03:08:29 -0700 (PDT)
In-Reply-To: <20110519232827.GA969@shareable.org>
References: <ED13A76FCE9E96498B049688227AEA292C6A81E4@TK5EX14MBXC206.redmond.corp.microsoft.com> <F390D8D1-335B-4595-93A2-0741DD693559@gmail.com> <ED13A76FCE9E96498B049688227AEA292C6A85DE@TK5EX14MBXC206.redmond.corp.microsoft.com> <BANLkTimg6Z8rs+SDp-HX+FzJQukKndWqkg@mail.gmail.com> <20110519232827.GA969@shareable.org>
From: Pieter Hintjens <ph@imatix.com>
Date: Fri, 20 May 2011 12:08:29 +0200
X-Google-Sender-Auth: 9As2FKsQrTmnnB3he_-B3PfPX7U
Message-ID: <BANLkTinAzZxAojTUDAz3X69=odAQ+xse_g@mail.gmail.com>
To: Jamie Lokier <jamie@shareable.org>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: "hybi@ietf.org" <hybi@ietf.org>, Greg Wilkins <gregw@intalio.com>, Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>
Subject: Re: [hybi] Ping/Pong body (was Re: TSV-Directorate review of draft-ietf-hybi-thewebsocketprotocol-07)
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: Fri, 20 May 2011 10:08:50 -0000

On Fri, May 20, 2011 at 1:28 AM, Jamie Lokier <jamie@shareable.org> wrote:

> If the client had to wait for pong before sending another ping, that
> would cause spurious "offline" statuses whenever there was a lot of
> data transiting in server-to-client direction.

We had exactly this problem in AMQP and resolved it quite effectively
by treating _any_ incoming data as a liveness indicator. Any reason
you'd not do this?

-Pieter Hintjens

v2.23.0 | Report a Bug | By Email