[hybi] WS & Nagle in use

"Greg Longtin" <Greg@ChampionEnt.net> Mon, 21 March 2011 13:17 UTC

Return-Path: <Greg@ChampionEnt.net>
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 6A0203A685D for <hybi@core3.amsl.com>; Mon, 21 Mar 2011 06:17:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[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 uxNfwE38VtlL for <hybi@core3.amsl.com>; Mon, 21 Mar 2011 06:17:33 -0700 (PDT)
Received: from smtpout-2.iphouse.net (smtpout-2.iphouse.net [209.240.70.141]) by core3.amsl.com (Postfix) with ESMTP id AE6E13A685A for <hybi@ietf.org>; Mon, 21 Mar 2011 06:17:33 -0700 (PDT)
Received: from smtpout-2.iphouse.net (localhost [127.0.0.1]) by outbound-clamsmtpd.iphouse.net (Postfix) with ESMTP id 21E361CD26 for <hybi@ietf.org>; Mon, 21 Mar 2011 08:19:05 -0500 (CDT)
Received: from GJL8710w (longtin.dsl.visi.com [209.98.144.159]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtpout-2.iphouse.net (Postfix) with ESMTPSA id BFF911CD13 for <hybi@ietf.org>; Mon, 21 Mar 2011 08:19:04 -0500 (CDT)
From: Greg Longtin <Greg@ChampionEnt.net>
To: hybi <hybi@ietf.org>
Date: Mon, 21 Mar 2011 08:19:03 -0500
Message-ID: <001701cbe7ca$8d345be0$a79d13a0$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcvnyoyhTIdkCtEHT9CALrmDK5v+hA==
Content-Language: en-us
X-Virus-Scanned: ClamAV using ClamSMTP
Subject: [hybi] WS & Nagle in use
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, 21 Mar 2011 13:17:34 -0000

To all,

Good day.  Previously, I asked that WS should disable Nagle, or the API
might allow control of it.  This weekend I thought of the converse.

Not being familiar with all OS's, I'm not sure if, now or in the future,
administrative control may affect whether Nagle can be controlled at an app
level.

Hence, should the specs state clearly that if a server or client WS
application receives a 'multiple message' Nagle packet, that all messages
should be decoded from it?

In my testing, I'm not sure if the current clients did so.  Should I test
the Minefield and Silverlight implementations, or are we certain that they
do so?
 
Thanks,

Greg