NNG_MSG(5)

💌 NAME 💌

nng_msg — the message, bestie. the actual lil packet of vibes.

---

✨ SYNOPSIS ✨

#include <nng/nng.h>

typedef struct nng_msg nng_msg;

---

🦋 DESCRIPTION 🦋

okay so picture this: an nng_msg is one single message sent between Scalability Protocols peers. that's the whole job. one message, one vibe.

and inside? she's got layers 💅:

• a body — this holds the application supplied payload, aka the actual content you care about
• a header — this holds protocol specific routing and similar related information

so yeah, the body is the main character and the header is the backstage crew making sure everything gets where it's going. 🎀

✨ Tip ✨ using message-oriented functions is a good way to reduce the likelihood of data copies and improve application performance. no cap, it's giving efficiency. 🔥

messages get allocated with the nng_msg_alloc() function, and they get deallocated with the nng_msg_free() function. that's the birth and the farewell, iconically. 🫶

---

and there's more — other functions exist to access message contents, including:

• adding data to either the beginning or the end of the message
• automatic data conversion
• 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. the way that these lil functions just dodge the copies entirely... genuinely obsessed. 💖

---

👑 SEE ALSO 👑

• nng_aio_get_msg(3)
• nng_aio_set_msg(3)
• nng_msg_alloc(3)
• nng_msg_body(3)
• nng_msg_dup(3)
• nng_msg_free(3)
• nng_msg_header(3)
• nng_msg_header_len(3)
• nng_msg_len(3)
• nng_msg_capacity(3)
• nng_msg_reserve(3)
• nng_msg_realloc(3)
• nng_recvmsg(3)
• nng_sendmsg(3)
• nng_strerror(3)
• nng(7)

---

that's the whole page bestie, stan nng_msg, periodt 💅✨

this was NNG_MSG(5) from the NNG Reference Manual, dated 2026-06-30 — mwah, love u, go read the rest of the NNG reference manual, iykyk 🎀🦋