From: Kim F. Storm <storm@cua.dk>
Date: Fri, 10 Oct 2003 21:35:51 +0000 (+0000)
Subject: (Network): Introduce make-network-process.
X-Git-Tag: ttn-vms-21-2-B4~8569
X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=78e54e2d68737ca1c7175e4b9c1455e77025b388;p=emacs.git

(Network): Introduce make-network-process.
---

diff --git a/lispref/processes.texi b/lispref/processes.texi
index 7165c9634c2..a13dfbab3a8 100644
--- a/lispref/processes.texi
+++ b/lispref/processes.texi
@@ -1494,6 +1494,15 @@ made.  (The network connection inherits certain information, including
 the process plist, from the server.)  The network server then goes
 back to listening for more connection requests.
 
+  Network connections and servers are created by calling
+@code{make-network-process} with an argument list consisting of
+keyword/argument pairs, for example @code{:server t} to create a
+server process, or @code{:type 'datagram} to create a datagram
+connection.  @xref{Low-Level Network} for details.  You can also use
+one of the @code{open-network-...} functions descibed below;
+internally, they just call @code{make-network-process} with suitable
+arguments.
+
   You can distinguish process objects representing network connections
 and servers from those representing subprocesses with the
 @code{process-status} function.  The possible status values for