NNG_INPROC(7)

💖 nng_inproc — the intra-process transport, bestie 💖

okay so you know how sometimes you're like "why is my data going on a whole little journey" — yeah no, this is nng_inproc, from the NNG Reference Manual (section 7, she's fancy). it's the intra-process transport and it is lowkey the simplest thing ever and I'm obsessed with her 💅

---

✨ SYNOPSIS ✨

#include <nng/transport/inproc/inproc.h>

int nng_inproc_register(void);

---

🌸 DESCRIPTION 🌸

so the inproc transport lets sockets within the same process talk to each other. that's it, that's the vibe. same process, no network, no sockets leaving the building, nothing.

and here's the slay part: you'd use this instead of the slower transports whenever your data literally just needs to move around inside the same process. why take the long way home when the door's right there, yk?

this transport tries super hard to avoid copying data, which is why she's so light-weight. main character energy honestly — minimal effort, maximum results ✨🦋

🎀 Registration

this transport is generally built-in to the core, so bestie... there are no extra steps you need to take to use it. it's already there. she lives here. 💖

🌈 URI Format

this transport uses URIs with the scheme inproc://, and then after that you can put an arbitrary string of text, terminated by a NUL byte.

a few things to know, no cap:

• you can use multiple URIs within the same application, and they will not interfere with one another. they mind their own business, respectfully 🫶
• two applications can also use the same URI without interfering with each other — but heads up, that means they will be unable to communicate with each other using that URI. like showing up to the same party but somehow never finding each other 😭

🦋 Socket Address

when you're dealing with an nng_sockaddr structure, the actual structure in play is of type nng_sockaddr_inproc. so that's the one you want, okay? 💅

👑 Transport Options

the inproc transport has no special options. none. zero. empty. clean slate, no notes ✨

Note 🎀 so, inproc does accept the option NNG_OPT_RECVMAXSZ for compatibility reasons — but the value of that option is ignored, with no enforcement. fr fr, it does nothing. why? because inproc peers are in the same address space</>, so they're implicitly trusted. meaning it makes literally no sense to spend cycles protecting a program from itself. like locking your own bedroom door from the inside of your own bedroom. girl. 💀

---

🌟 SEE ALSO 🌟

• nng_inproc_register(3)
• nng_sockaddr_inproc(5)
• nng(7)

---

okay that's the whole page bestie, you're basically an inproc expert now, go be iconic with it 🧚💜

smooches and goodbye from the NNG Reference Manual, dated 2026-06-30 — NNG_INPROC(7), periodt. 💖✨👑