= nng_msg_alloc(3) // // Copyright 2018 Staysail Systems, Inc. // Copyright 2018 Capitar IT Group BV // // This document is supplied under the terms of the MIT License, a // copy of which should be located in the distribution where this // file was obtained (LICENSE.txt). A copy of the license may also be // found online at https://opensource.org/licenses/MIT. // == NAME nng_msg - message == SYNOPSIS [source, c] ---- #include typedef struct nng_msg nng_msg; ---- == DESCRIPTION An `nng_msg` represents a single ((message)) sent between Scalability Protocols peers. Messages internally have a ((body)), containing the application supplied payload, and a ((header)), containing protocol specific routing and similar related information. TIP: Using the message-oriented functions in the <> API is a good way to reduce the likelihood of data copies and improve application performance. Messages are allocated using the `<>` function, and are deallocated using the `<>` function. In addition there are other functions used to access message contents, including adding data to either the beginning or end of the message, automatic data conversion, and removing data from the beginning or end. These functions are designed to try to avoid copying message contents by making use of scratch areas at the beginning and end of the message. == RETURN VALUES This function returns 0 on success, and non-zero otherwise. == ERRORS [horizontal] `NNG_ENOMEM`:: Insufficient free memory exists to allocate a message. == SEE ALSO [.text-left] <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>