From 754bbf7a25a8dda49b5d08ef0d0443bbf5af0e36 Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Sun, 7 Apr 2024 13:41:34 -0500 Subject: new repository --- devdocs/elisp/datagrams.html | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 devdocs/elisp/datagrams.html (limited to 'devdocs/elisp/datagrams.html') diff --git a/devdocs/elisp/datagrams.html b/devdocs/elisp/datagrams.html new file mode 100644 index 00000000..b91be763 --- /dev/null +++ b/devdocs/elisp/datagrams.html @@ -0,0 +1,10 @@ +

Datagrams

A datagram connection communicates with individual packets rather than streams of data. Each call to process-send sends one datagram packet (see Input to Processes), and each datagram received results in one call to the filter function.

The datagram connection doesn’t have to talk with the same remote peer all the time. It has a remote peer address which specifies where to send datagrams to. Each time an incoming datagram is passed to the filter function, the peer address is set to the address that datagram came from; that way, if the filter function sends a datagram, it will go back to that place. You can specify the remote peer address when you create the datagram connection using the :remote keyword. You can change it later on by calling set-process-datagram-address.

Function: process-datagram-address process +

If process is a datagram connection or server, this function returns its remote peer address.

+
Function: set-process-datagram-address process address +

If process is a datagram connection or server, this function sets its remote peer address to address.

+
+

+ Copyright © 1990-1996, 1998-2022 Free Software Foundation, Inc.
Licensed under the GNU GPL license.
+ https://www.gnu.org/software/emacs/manual/html_node/elisp/Datagrams.html +

+
-- cgit v1.2.3