changeset 52695:e5c94aabfe90

(Network): Say what stopped datagram connections do.
author Richard M. Stallman <rms@gnu.org>
date Tue, 30 Sep 2003 13:01:12 +0000
parents 3c9835a0d5b4
children 7f1977773296
files lispref/processes.texi
diffstat 1 files changed, 5 insertions(+), 4 deletions(-) [+]
line wrap: on
line diff
--- a/lispref/processes.texi	Tue Sep 30 13:00:23 2003 +0000
+++ b/lispref/processes.texi	Tue Sep 30 13:01:12 2003 +0000
@@ -1507,11 +1507,12 @@
 process, being stopped means not accepting new connections.  (Up to 5
 connection requests will be queued for when you resume the server; you
 can increase this limit, unless it is imposed by the operating
-systems.)  For a network connection, being stopped means not
+systems.)  For a network stream connection, being stopped means not
 processing input (any arriving input waits until you resume the
-connection).  You can use the function @code{process-command} to
-determine whether a network connection or server is stopped; a
-non-@code{nil} value means yes.
+connection).  For a datagram connection, some number of packets may be
+queued but input may be lost.  You can use the function
+@code{process-command} to determine whether a network connection or
+server is stopped; a non-@code{nil} value means yes.
 
 @defun open-network-stream name buffer-or-name host service
 This function opens a TCP connection, and returns a process object