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 message-oriented functions is a good way to reduce the likelihood of data copies and improve application performance. |
Messages are allocated using the nng_msg_alloc()
function, and are deallocated using the nng_msg_free()
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.