Date: Sat, 30 Jan 1999 14:26:46 -0500 (EST) From: Jamie Howard <howardjp@dragon.ham.muohio.edu> To: Cory Kempf <ckempf@enigami.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: socketpair(2) Message-ID: <Pine.LNX.4.05.9901301416450.12383-100000@dragon.ham.muohio.edu> In-Reply-To: <x7hft8fybv.fsf@singularity.enigami.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 30 Jan 1999, Cory Kempf wrote: > socketpair(2) only works with unix domain sockets, not inet domain sockets. > It is a hack to allow the creation of pair of connected sockets. This is only > useful when both client and server live on the same machine. If you want > internet domain sockets, you will need to go throught the > socket/bind/connect/listen/accept mechanism. Right, but it seems as though a UNIX domain socket will allow a process to read off the socket that which it has just written, when bidirectional, correct? (Or am I doing something wrong?) It would be nice if two connected processes could send data back and forth without reading off their own output, and a TCP connection implements this. (I think this is similar to a channel under Plan 9/Alef, but I do not know for certain due to lack of access.) Have I missed something here? Additionally, this is something of a learning experience, to an extent, it doesn't matter how usefull the function is, the more important issue is can I implement it without screwing up too badly? :) Jamie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.05.9901301416450.12383-100000>