openssh unix dev - Jan 2002 - Use of TCP_NODELAY in commercial SSH

In order to test my overlapping request path for sftp on another ssh 
server, I downloaded ssh2 version 3.1.0 from ssh.com.  Having downloaded 
it, I decided to study the use of TCP_NODELAY in that implementation.  
Here's what I found:

* Both ssh2 and sshd2 has a NoDelay config option which is false by 
  default.

* The ssh2 client does not enable or disable NoDelay because of a channel
  type (such as pty or X11).

* The sftp2 client uses "-o NoDelay=yes" when starting its ssh
"proxy"
  which helps get, but not put.

* The sftp2 server does not enable NoDelay (since there is no way to do so 
  I guess).

/Tobias

On Thu, Jan 31, 2002 at 10:29:51PM +0100, Tobias Ringstrom
wrote:
> In order to test my overlapping request path for sftp on another ssh 
> server, I downloaded ssh2 version 3.1.0 from ssh.com.  Having downloaded 
> it, I decided to study the use of TCP_NODELAY in that implementation.  
> Here's what I found:
More evidence for the need to have messages at the SSHv2 layer to handle
setting/unsetting TCP_NODELAY.

:)
> /Tobias

Nico
--
-DISCLAIMER: an automatically appended disclaimer may follow. By posting-
-to a public e-mail mailing list I hereby grant permission to distribute-
-and copy this message.-

Visit our website at http://www.ubswarburg.com

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.