Document Transaction TCP extensions to generic system calls.

lib/libc/sys/send.2

@@ -29,9 +29,10 @@
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
-.\"     @(#)send.2	8.2 (Berkeley) 2/21/94
+.\"     From: @(#)send.2	8.2 (Berkeley) 2/21/94
+.\"	$Id$
 .\"
-.Dd February 21, 1994
+.Dd February 15, 1995
 .Dt SEND 2
 .Os BSD 4.2
 .Sh NAME
@@ -94,8 +95,11 @@ The
 .Fa flags
 parameter may include one or more of the following:
 .Bd -literal
-#define	MSG_OOB        0x1  /* process out-of-band data */
+#define	MSG_OOB		0x1   /* process out-of-band data */
-#define	MSG_DONTROUTE  0x4  /* bypass routing, use direct interface */
+#define	MSG_PEEK	0x2   /* peek at incoming message */
+#define	MSG_DONTROUTE	0x4   /* bypass routing, use direct interface */
+#define MSG_EOR		0x8   /* data completes record */
+#define	MSG_EOF		0x100 /* data completes transaction */
 .Ed
 .Pp
 The flag
@@ -107,6 +111,20 @@ data on sockets that support this notion (e.g.
 the underlying protocol must also support
 .Dq out-of-band
 data.
+.Dv MSG_EOR
+is used to indicate a record mark for protocols which support the
+concept.
+.Dv MSG_EOF
+requests that the sender side of a socket be shut down, and that an
+appropriate indication be sent at the end of the specified data;
+this flag is only implemented for
+.Dv SOCK_STREAM
+sockets in the
+.Dv PF_INET
+protocol family, and is used to implement Transaction
+.Tn TCP
+(see
+.Xr ttcp 4 ) .
 .Dv MSG_DONTROUTE
 is usually used only by diagnostic or routing programs.
 .Pp

lib/libc/sys/socket.2

@@ -29,9 +29,10 @@
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
-.\"     @(#)socket.2	8.1 (Berkeley) 6/4/93
+.\"     From: @(#)socket.2	8.1 (Berkeley) 6/4/93
+.\"	$Id$
 .\"
-.Dd June 4, 1993
+.Dd February 15, 1995
 .Dt SOCKET 2
 .Os BSD 4.2
 .Sh NAME
@@ -56,11 +57,12 @@ These families are defined in the include file
 The currently understood formats are
 .Pp
 .Bd -literal -offset indent -compact
-AF_UNIX		(UNIX internal protocols),
+PF_LOCAL	(Host-internal protocols, formerly called PF_UNIX),
-AF_INET		(ARPA Internet protocols),
+PF_INET		(ARPA Internet protocols),
-AF_ISO		(ISO protocols),
+PF_ISO		(ISO protocols),
-AF_NS		(Xerox Network Systems protocols), and
+PF_CCITT	(ITU-T protocols, like X.25),
-AF_IMPLINK	(IMP \*(lqhost at IMP\*(rq link layer).
+PF_NS		(Xerox Network Systems protocols), and
+.\"PF_IMPLINK	(IMP \*(lqhost at IMP\*(rq link layer).
 .Ed
 .Pp
 The socket has the indicated
@@ -123,7 +125,8 @@ to pipes.  A stream socket must be in a
 state before any data may be sent or received
 on it.  A connection to another socket is created with a
 .Xr connect 2
-call.  Once connected, data may be transferred using
+call.
+Once connected, data may be transferred using
 .Xr read 2
 and
 .Xr write 2
@@ -131,7 +134,15 @@ calls or some variant of the
 .Xr send 2
 and
 .Xr recv 2
-calls.  When a session has been completed a
+calls.
+(Some protocol families, such as the Internet family,
+support the notion of an
+.Dq implied connect,
+which permits data to be sent piggybacked onto a connect operation by
+using the
+.Xr sendto 2
+call.)
+When a session has been completed a
 .Xr close 2
 may be performed.
 Out-of-band data may also be transmitted as described in
@@ -244,11 +255,13 @@ The socket cannot be created until sufficient resources are freed.
 .Xr write 2
 .Rs
 .%T "An Introductory 4.3 BSD Interprocess Communication Tutorial"
-.%O "reprinted in UNIX Programmer's Supplementary Documents Volume 1"
+.%B PS1
+.%N 7
 .Re
 .Rs
 .%T "BSD Interprocess Communication Tutorial"
-.%O "reprinted in UNIX Programmer's Supplementary Documents Volume 1"
+.%B PS1
+.%N 8
 .Re
 .Sh HISTORY
 The