IETF Logo Mail Archive

Re: [hybi] WebSocket & Nagle

Andy Green <andy@warmcat.com> Fri, 18 March 2011 19:09 UTC

Return-Path: <andy.warmcat.com@googlemail.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 DBE423A6A08 for <hybi@core3.amsl.com>; Fri, 18 Mar 2011 12:09:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.587
X-Spam-Level:
X-Spam-Status: No, score=-3.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, 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 gI+-HN89lprc for <hybi@core3.amsl.com>; Fri, 18 Mar 2011 12:09:12 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 9900B3A6999 for <hybi@ietf.org>; Fri, 18 Mar 2011 12:09:12 -0700 (PDT)
Received: by wwa36 with SMTP id 36so3532455wwa.13 for <hybi@ietf.org>; Fri, 18 Mar 2011 12:10:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=2xLnHiGRAUXY+N4ieAyTGRvLiioXYBU1RvBMLa3PWjU=; b=Ftk4++9Pgo5eYEByeVe/fAcolZOqdPJGJhjmzXwwv/ybITORe0civf2Ix1tT5YR6Vv R/umd3jXrTSjvbqyeXkSNMxT87IFU1zw2ECV3XLi73veaTvx1m6Y6fMecBikgbCEb+Ps h/F5uxZ5FBhlM5HWQNIzYtVfdrhlC4cE3RzuY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=WuwDJpv0n7uB546BOsHXXIc8SFBaCtgHGDgnJUqhm0NuowG98CjRtz4NtzbJUctj+R aVuVIMn4pn8FjvDoNrJ7j1PCrwylhSEuUxfA2FoLWi3A5zMcfVdN/NTwl/EHKQxXx60n E2OKuovC4JP29Qe5ozvDkQk0WX4fCJYVRsC+4=
Received: by 10.227.196.2 with SMTP id ee2mr1557486wbb.129.1300475441320; Fri, 18 Mar 2011 12:10:41 -0700 (PDT)
Received: from otae.warmcat.com (s15404224.onlinehome-server.info [87.106.134.80]) by mx.google.com with ESMTPS id bd8sm1504312wbb.35.2011.03.18.12.10.39 (version=SSLv3 cipher=OTHER); Fri, 18 Mar 2011 12:10:40 -0700 (PDT)
Sender: Andy Green <andy.warmcat.com@googlemail.com>
Message-ID: <4D83AE2E.7080008@warmcat.com>
Date: Fri, 18 Mar 2011 19:10:38 +0000
From: Andy Green <andy@warmcat.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15) Gecko/20110310 Fedora/3.1.9-2.fc16 Thunderbird/3.1.9
MIME-Version: 1.0
To: Greg Longtin <Greg@ChampionEnt.net>
References: <000501cbe59a$62701cf0$275056d0$@net>
In-Reply-To: <000501cbe59a$62701cf0$275056d0$@net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: hybi <hybi@ietf.org>
Subject: Re: [hybi] WebSocket & Nagle
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: Fri, 18 Mar 2011 19:09:14 -0000

On 03/18/2011 06:29 PM, Somebody in the thread at some point said:

Hi -

> I have been working with WebSocket, based on it being a browser based socket
> interface for intranet use.
>
> I've created a Windows server, and have been testing with the MSFT 05 and 06
> Silverlight prototypes and Pat McManus' WS 06 Minefield build (thank you.)
>
> I believe all three implementations allow the use of the Nagle algorithm for
> sending client packets.  On my system, this intermittently introduces a 200
> mS delay, along with the combining of packets.  IMHO, for many applications,
> that amount of delay isn't acceptable.
>
> I'm not an Internet network type, so I'm not familiar with implications at
> that level.
>
>  From my perspective, it would be best if either Nagle was disabled for
> WebSocket packets, or the browser script API would allow one to do so.  I
> realize that option is outside of hybi spec.

libwebsockets also kills Nagling.  Nagle can lead to what is basically 
5Hz service which is "not the right thing".

-Andy

v2.23.0 | Report a Bug | By Email