diff options
| author | Henrik Nord <[email protected]> | 2014-11-20 10:34:30 +0100 |
|---|---|---|
| committer | Henrik Nord <[email protected]> | 2014-11-20 10:34:30 +0100 |
| commit | cb372c96f3449cfca69e2737fa3d4503fa24444a (patch) | |
| tree | aebe5eb6b57be4527427d22983ca2e9f3bf6bdf7 /lib/stdlib/doc | |
| parent | 2feb7638d47f2d1012871de3040fa7d50f058e3a (diff) | |
| parent | 69e8387629bdea141e196c515f4d9381f7ac3e18 (diff) | |
| download | otp-cb372c96f3449cfca69e2737fa3d4503fa24444a.tar.gz otp-cb372c96f3449cfca69e2737fa3d4503fa24444a.tar.bz2 otp-cb372c96f3449cfca69e2737fa3d4503fa24444a.zip | |
Merge branch 'legoscia/io-message-queue-optimisation' into maint
* legoscia/io-message-queue-optimisation:
Optimise io requests for long message queues
Diffstat (limited to 'lib/stdlib/doc')
| -rw-r--r-- | lib/stdlib/doc/src/io_protocol.xml | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/lib/stdlib/doc/src/io_protocol.xml b/lib/stdlib/doc/src/io_protocol.xml index 9328704e11..d6da205f07 100644 --- a/lib/stdlib/doc/src/io_protocol.xml +++ b/lib/stdlib/doc/src/io_protocol.xml @@ -76,10 +76,11 @@ the server eventually sends a corresponding <c>io_reply</c> tuple.</p> the I/O server sends the IO reply to.</item> <item><c>ReplyAs</c> can be any datum and is returned in the corresponding -<c>io_reply</c>. The <seealso marker="stdlib:io">io</seealso> module simply uses the pid() -of the I/O server as the <c>ReplyAs</c> datum, but a more complicated client +<c>io_reply</c>. The <seealso marker="stdlib:io">io</seealso> module monitors +the I/O server, and uses the monitor reference as the <c>ReplyAs</c> datum. +A more complicated client could have several outstanding I/O requests to the same I/O server and -would then use i.e. a <c>reference()</c> or something else to differentiate among +would then use different references (or something else) to differentiate among the incoming IO replies. The <c>ReplyAs</c> element should be considered opaque by the I/O server. Note that the <c>pid()</c> of the I/O server is not explicitly present in the <c>io_reply</c> tuple. The reply can be sent from any |