From 6e01408aba71e26884c5db81b8e4fa89bd803576 Mon Sep 17 00:00:00 2001
From: Rickard Green
Date: Fri, 21 Sep 2012 15:12:07 +0200
Subject: Implement true asynchronous signaling between processes and ports
---
system/doc/reference_manual/ports.xml | 13 +++++++++----
1 file changed, 9 insertions(+), 4 deletions(-)
(limited to 'system/doc/reference_manual')
diff --git a/system/doc/reference_manual/ports.xml b/system/doc/reference_manual/ports.xml
index 4847dd67cd..c4e4ef1d35 100644
--- a/system/doc/reference_manual/ports.xml
+++ b/system/doc/reference_manual/ports.xml
@@ -87,8 +87,14 @@
of bytes, the option binary must be included.
The port owner Pid can communicate with the port
Port by sending and receiving messages. (In fact, any
- process can send the messages to the port, but the messages from
- the port always go to the port owner).
+ process can send the messages to the port, but the port owner must
+ be identified in the message).
+ As of OTP-R16 messages sent to ports are delivered truly
+ asynchronously. The underlying implementation previously
+ delivered messages to ports synchronously. Message passing has
+ however always been documented as an asynchronous operation, so
+ this should not be an issue for an Erlang program communicating
+ with ports, unless false assumptions about ports has been made.
Below, Data must be an I/O list. An I/O list is a binary
or a (possibly deep) list of binaries or integers in the range
0..255.
@@ -127,8 +133,7 @@
Messages Received From a Port.
Instead of sending and receiving messages, there are also a
- number of BIFs that can be used. These can be called by any
- process, not only the port owner.
+ number of BIFs that can be used.
port_command(Port,Data) |
--
cgit v1.2.3