Date: Tue, 31 Aug 2010 22:32:56 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Andre Oppermann <andre@freebsd.org> Cc: freebsd-net@freebsd.org Subject: Re: Removal of deprecated implied connect for TCP Message-ID: <alpine.BSF.2.00.1008312228540.90811@fledge.watson.org> In-Reply-To: <4C7D0089.1020104@freebsd.org> References: <4C7A7B25.9040300@freebsd.org> <alpine.BSF.2.00.1008311102220.22661@fledge.watson.org> <4C7D0089.1020104@freebsd.org>
index | next in thread | previous in thread | raw e-mail
On Tue, 31 Aug 2010, Andre Oppermann wrote: >> I'm not entirely comfortable with this change, and would like a chance to >> cogitate on it a bit more. While I'm not aware of any applications >> depending on the semantic for TCP, I know that we do use it for UNIX domain >> sockets. > > I don't have any plans to remove the implied connect support from the socket > layer or other protocols, only from TCP. Right -- the implicit question is: why should TCP be the only stream protocol in our stack *not* to support implied connection, when we plan to continue to support it for all other protocols? > For deprecating this part of the TCP API there is no documentation to the > implied connect in tcp(4). In sendto(2) it doesn't differentiate between > protocols and simply says: "... sendto() and sendmsg() may be used at any > time." For MSG_EOF it says that is only supported for SOCK_STREAM sockets > in the PF_INET protocol family. These sentences have to be corrected. In general, deprecating is taken to mean providing significant and explicit advance warning of removal -- for example, updating the 8.x man page to point out that the feature is deprecated and it will not appear in future releases of FreeBSD. Roberthome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1008312228540.90811>