From owner-freebsd-hackers Fri Mar 17 14:51:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 2C74B37B632 for ; Fri, 17 Mar 2000 14:51:22 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 17 Mar 2000 22:51:21 +0000 (GMT) To: James FitzGibbon Cc: hackers@freebsd.org Subject: Re: T/TCP friendly inetd change? In-reply-to: Your message of "Fri, 17 Mar 2000 09:46:35 EST." <20000317094635.B41950@targetnet.com> X-Request-Do: Date: Fri, 17 Mar 2000 22:51:20 +0000 From: David Malone Message-ID: <200003172251.aa89166@salmon.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I like T/TCP (I use it on some of my networked apps for the same reasons you > describe), but I don't think that it should be added to a program like inetd > which has two default settings that would need to be changed before the > T/TCP extensions would ever provide any benefit. The changes I've suggested don't actually require T/TCP to be useful, they just make inetd friendlier to T/TCP connections if they come in. When T/TCP isn't used they just put the FIN for the TCP connection on the last data packet, instead of on a seperate packet, so saving one packet. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message