From f723fa9655e1e7fadc1a15b94b66de674ab9fe17 Mon Sep 17 00:00:00 2001 From: Garrett D'Amore Date: Wed, 13 Mar 2019 00:50:48 -0700 Subject: fixes #815 Eliminate socket filters on message queues This also eliminates the enforcement of NNG_OPT_RECVMAXSZ for inproc, which never really made much sense. This helps inproc go faster. While here, also clean up the entry point for protocols to support a drain option, since we don't use that anywhere. --- docs/man/nng_inproc.7.adoc | 18 ++++++++++++------ 1 file changed, 12 insertions(+), 6 deletions(-) (limited to 'docs') diff --git a/docs/man/nng_inproc.7.adoc b/docs/man/nng_inproc.7.adoc index cfd3806d..733b7789 100644 --- a/docs/man/nng_inproc.7.adoc +++ b/docs/man/nng_inproc.7.adoc @@ -1,6 +1,6 @@ = nng_inproc(7) // -// Copyright 2018 Staysail Systems, Inc. +// Copyright 2019 Staysail Systems, Inc. // Copyright 2018 Capitar IT Group BV // // This document is supplied under the terms of the MIT License, a @@ -53,17 +53,23 @@ that URI. === Socket Address -When using an `<>` structure, +When using an xref:nng_sockaddr.5.adoc[`nng_sockaddr`] structure, the actual structure is of type -`<>`. +xref:nng_sockaddr_inproc.5.adoc[`nng_sockaddr_inproc`]. === Transport Options The _inproc_ transport has no special options. +NOTE: While _inproc_ accepts the option +xref:nng_options.5.adoc#NNG_OPT_RECVMAXSZ[`NNG_OPT_RECVMAXSZ`] for +compatibility, the value of the option is ignored with no enforcement. +As _inproc_ peers are in the same address space, they are implicitly trusted, +and thus it makes no sense to spend cycles protecting a program from itself. + == SEE ALSO [.text-left] -<>, -<>, -<> +xref:nng_inproc_register.3.adoc[nng_inproc_register(3)], +xref:nng_sockaddr_inproc.5.adoc[nng_sockaddr_inproc(5)], +xref:nng.7.adoc[nng(7)] -- cgit v1.2.3-70-g09d2