diff options
| author | gdamore <gdamore@users.noreply.github.com> | 2025-10-09 02:03:21 +0000 |
|---|---|---|
| committer | gdamore <gdamore@users.noreply.github.com> | 2025-10-09 02:03:21 +0000 |
| commit | a35e8745f354e5569a4416869e755934fff717b4 (patch) | |
| tree | a0434619eaa257f31f2a92bf97efb79f719558bc /ref/tran/inproc.html | |
| parent | 426ace3a013e7bc779686689d41f011178a26cc6 (diff) | |
| download | nng-a35e8745f354e5569a4416869e755934fff717b4.tar.gz nng-a35e8745f354e5569a4416869e755934fff717b4.tar.bz2 nng-a35e8745f354e5569a4416869e755934fff717b4.zip | |
deploy: bdf85dd692d803b7b2fc793f1c7723f9874bfcdb
Diffstat (limited to 'ref/tran/inproc.html')
| -rw-r--r-- | ref/tran/inproc.html | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/ref/tran/inproc.html b/ref/tran/inproc.html index a17835a4..180182cf 100644 --- a/ref/tran/inproc.html +++ b/ref/tran/inproc.html @@ -266,15 +266,15 @@ They will however be unable to communicate with each other using that URL.</p> <span class="mdbook-alerts-icon"></span> note </p> -<p>While <em>inproc</em> accepts the option <code>NNG_OPT_RECVMAXSZ</code> for +<p>While <em>inproc</em> accepts the option <a href="../api/sock.html#NNG_OPT_RECVMAXSZ"><code>NNG_OPT_RECVMAXSZ</code></a> for compatibility, the value of the option is ignored with no enforcement. As <em>inproc</em> peers are in the same address space, they are implicitly trusted, so the protection afforded by <code>NNG_OPT_RECVMAXSZ</code> is unnecessary.</p> </div> <h2 id="mixing-implementations"><a class="header" href="#mixing-implementations">Mixing Implementations</a></h2> <p>When mixing the <em>NNG</em> library with other implementations of these -protocols in the same process (such as the <em>mangos</em> -or <em>libnanomsg</em> implementations), it will not be possible to utilize +protocols in the same process (such as the <a href="https://github.com/nanomsg/mangos">mangos</a> +or <a href="https://github.com/nanomsg/nanomsg">libnanomsg</a> implementations), it will not be possible to utilize the <em>inproc</em> transport to communicate across this boundary.</p> <p>This limitation also extends to using different instances of the <em>NNG</em> library within the same process.</p> |