From owner-freebsd-hackers  Fri Nov 15 09:34:59 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id JAA01697
          for hackers-outgoing; Fri, 15 Nov 1996 09:34:59 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA01686
          for <hackers@freebsd.org>; Fri, 15 Nov 1996 09:34:48 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA26294; Fri, 15 Nov 1996 10:19:50 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199611151719.KAA26294@phaeton.artisoft.com>
Subject: Re: Sockets question...
To: jdp@polstra.com (John Polstra)
Date: Fri, 15 Nov 1996 10:19:50 -0700 (MST)
Cc: karl@Mcs.Net, scrappy@ki.net, jgreco@brasil.moneng.mei.com,
        hackers@freebsd.org
In-Reply-To: <199611150258.SAA12064@austin.polstra.com> from "John Polstra" at Nov 14, 96 06:58:11 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> If the socket is not in non-blocking mode, and you do a write(2) of N
> bytes to it, and the write call returns anything other than -1 or N,
> then that is a bug.

You mean "blocking" mode, right?


> If the sending socket returns N, but not all of the data gets to
> the receiving socket, then that is either a bug or a network problem.

Yes.  This is an acceptable event.

However, the receiver should then not have "all frags received" and
therfore a *blocking* read on the receiving socket should hang.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.