Date: Thu, 21 Oct 2004 11:51:37 -0700 From: "David O'Brien" <obrien@freebsd.org> To: Andre Oppermann <andre@freebsd.org> Cc: freebsd-arch@freebsd.org Subject: Re: Removing T/TCP and replacing it with something simpler Message-ID: <20041021185137.GA37500@dragon.nuxi.com> In-Reply-To: <4177C8AD.6060706@freebsd.org> References: <4177C8AD.6060706@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Oct 21, 2004 at 04:33:17PM +0200, Andre Oppermann wrote: > I intend to remove T/TCP (transactional TCP) support from our TCP > implementation for the following reasons: .. Fine. > Thus after the removal of T/TCP for the reasons above I want to provide > a work-alike replacement for T/TCP's functionality: .. > This different implementation will be disabled by default and clearly > marked EXPERIMENTAL in a protocol sense. It will allow the only known > user of T/TCP to keep the same functionality with a very small change > to his application. It allows interesting new uses primarily in > Intranet environment where many short connections are openend in rapid > succession (LDAP servers, SQL servers, etc.). The modifications to > those programs to use the new option is minimal and requires only the > setting of the socket option, one setsockopt() call. I'm not so happy with a FreeBSD-only "proprietary" thing. Is there any proposed RFC work that provides the qualities you want? The advantage with T/TCP is that there was a published standard. -- -- David (obrien@FreeBSD.org)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041021185137.GA37500>