From 45f455064b5704f3d5ed8ecf9f197a18fe72ee59 Mon Sep 17 00:00:00 2001 From: Garrett D'Amore Date: Wed, 4 Apr 2018 12:37:34 -0700 Subject: fixes #331 replace NNG_OPT_RAW option with constructor This makes the raw mode something that is immutable, determined at socket construction. This is an enabling change for the separate context support coming soon. As a result, this is an API breaking change for users of the raw mode option (NNG_OPT_RAW). There aren't many of them out there. Cooked mode is entirely unaffected. There are changes to tests and documentation included. --- docs/man/nng_req.7.adoc | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) (limited to 'docs/man/nng_req.7.adoc') diff --git a/docs/man/nng_req.7.adoc b/docs/man/nng_req.7.adoc index 9d93eade..9b956172 100644 --- a/docs/man/nng_req.7.adoc +++ b/docs/man/nng_req.7.adoc @@ -16,11 +16,9 @@ nng_req - request protocol == SYNOPSIS [source,c] ----------- +---- #include - -int nng_req0_open(nng_socket *s); ----------- +---- == DESCRIPTION @@ -54,7 +52,7 @@ The _req_ protocol is the requester side, and the === Socket Operations -The <> call creates a requester socket. +The <> functions create a requester socket. This socket may be used to send messages (requests), and then to receive replies. Generally a reply can only be received after sending a request. @@ -70,8 +68,7 @@ that has already been placed on the wire. Attempts to receive on a socket with no outstanding requests will result in `NNG_ESTATE`. -Raw mode sockets (set with <>) -ignore all these restrictions. +<> mode sockets ignore all these restrictions. === Protocol Versions -- cgit v1.2.3-70-g09d2