Bug#525335: No way to reenable Nagle
retitle 525335 No way to reenable Nagle's algorithm (opposite of TCP_NODELAY) thanks From that, I guess you are referring to RFC 896. Is that correct? Yep, known is BSD sockets as the opposite of the TCP_NODELAY socket option. Juliusz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525335: No way to reenable Nagle
Package: openssh-server Version: 1:5.1p1-5 Both the ssh client and server disable Nagle's protocol on their sockets. There appears to be no way to reenable it (grep for set_nodelay in the source). For some protocols tunneled over ssh, it would be helpful if it were possible to reenable Nagle. This issue surfaced with the Darcs VCS, which typically uses ssh to communicate with the repository. Controlling Nagle should be done on the client, since only the client knows what the socket will be used for. However, it should control both the client and server socket, since the server socket usually transmits the bulk of the data. Juliusz Chroboczek pgppD0NGVHIZE.pgp Description: PGP signature
Bug#525335: No way to reenable Nagle
Hi Juliusz, On Thu, Apr 23, 2009 at 09:45:46PM +0200, Juliusz Chroboczek wrote: Both the ssh client and server disable Nagle's protocol on their sockets. There appears to be no way to reenable it (grep for set_nodelay in the source). I'm just an innocent bystander. I was confused by the above, because it sounded like Nagle was some kind of client/server package, and SSH broke its wire protocol. Not finding such a package in aptitude, I asked Wikipedia. From that, I guess you are referring to RFC 896. Is that correct? http://en.wikipedia.org/wiki/Nagle's_algorithm -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
