Re: [hybi] Encourage disabling Nagle in the standard text?

Andy Green <andy@warmcat.com> Wed, 19 April 2017 05:05 UTC

Return-Path: <andy@warmcat.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 77523131510 for <hybi@ietfa.amsl.com>; Tue, 18 Apr 2017 22:05:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MFx0tHsfRzJD for <hybi@ietfa.amsl.com>; Tue, 18 Apr 2017 22:05:01 -0700 (PDT)
Received: from mail.warmcat.com (mail.warmcat.com [163.172.24.82]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E0827126C83 for <hybi@ietf.org>; Tue, 18 Apr 2017 22:05:00 -0700 (PDT)
Date: Wed, 19 Apr 2017 13:04:48 +0800
In-Reply-To: <d44232f5-59cd-6e26-409e-7fd812245c5c@gmail.com>
References: <CAHixhFryAoF=no7_RkzxrkLFOSpSG3ACB1yBUtETp9A00sjsxw@mail.gmail.com> <B6D0F181-1482-4331-ADE1-FE92BE743208@warmcat.com> <d44232f5-59cd-6e26-409e-7fd812245c5c@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
To: hybi@ietf.org,Jacob Champion <champion.p@gmail.com>
From: Andy Green <andy@warmcat.com>
Message-ID: <B8D8870D-FF73-421B-99BA-0063D464D942@warmcat.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/hybi/z-IzNwPQGxDkOcBTwpOQCY9unZM>
Subject: Re: [hybi] Encourage disabling Nagle in the standard text?
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 19 Apr 2017 05:05:02 -0000


On April 19, 2017 12:09:35 PM GMT+08:00, Jacob Champion <champion.p@gmail.com> wrote:
>On 04/18/2017 07:57 PM, Andy Green wrote:
>> libwebsockets always disables Nagle...
>
>mod_websocket does too, simply because httpd disables it for all
>connections.
>
>> AFAIK there is no value to it for general ws use. But I dunno it
>> needs the standard changing, if things have higher than expected
>> latencies people will probably work it out for themselves.
>
>Yeah. Seems like it would be subprotocol-specific... if I write a
>Telnet
>clone over WebSocket, suddenly Nagle might make a lot of sense. But I'd
>have to make sure to TCP_CORK my control frames so that they got
>flushed
>through.

By coincidence in the last 3 weeks I have written both a telnet and an ssh server on top of libwebsockets (that runs on ESP32 via WLAN)... both work nicely without any special socket treatment and without nagle.

I think nagle can be helpful only under specific conditions, and over the years those conditions have become less of the norm.

-Andy

>
>See also
>https://www.ietf.org/mail-archive/web/hybi/current/msg06895.html .
>
>--Jacob
>
>_______________________________________________
>hybi mailing list
>hybi@ietf.org
>https://www.ietf.org/mailman/listinfo/hybi