From owner-freebsd-hackers Fri Nov 15 14:05:30 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA20298 for hackers-outgoing; Fri, 15 Nov 1996 14:05:30 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA20291 for ; Fri, 15 Nov 1996 14:05:23 -0800 (PST) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id OAA02629 for ; Fri, 15 Nov 1996 14:05:12 -0800 (PST) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <16531(3)>; Fri, 15 Nov 1996 14:02:43 PST Received: from localhost ([127.0.0.1]) by crevenia.parc.xerox.com with SMTP id <177557>; Fri, 15 Nov 1996 14:02:32 -0800 X-Mailer: exmh version 1.6.7 5/3/96 To: Terry Lambert cc: jgreco@brasil.moneng.mei.com (Joe Greco), jdp@polstra.com, scrappy@ki.net, hackers@freebsd.org Subject: Re: Sockets question... In-reply-to: Your message of "Fri, 15 Nov 1996 09:48:35 PST." <199611151748.KAA26388@phaeton.artisoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 15 Nov 1996 14:02:30 PST From: Bill Fenner Message-Id: <96Nov15.140232pst.177557@crevenia.parc.xerox.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199611151748.KAA26388@phaeton.artisoft.com> Terry wrote: >[long quote from socket man page] > >If you want to get technical, according to this description, if you are >using a SOCK_STREAM, then a read on a blocking socket will act like a >recv(2) or recvfrom(2) with flags MSG_WAITALL by default. That's a wild thing to get from that description. What I can get from that description is: - data is not lost or duplicated. - the connection is broken if data cannot be transmitted. - the connection can be optionally send keepalives in the absence of data. - an error is indicated if the keepalive fails. - SIGPIPE means you wrote on a closed socket. What part talks about how a blocking read works? >Maybe you should be using SOCK_SEQPACKET instead of SOCK_STREAM? There is no mapping from SOCK_SEQPACKET to an IP protocol. Maybe there will be if the IETF standardizes SFRP , but there is not today. Bill