NNG_TLS_CONFIG_HOLD(3tls)

💖 NAME 💖

nng_tls_config_hold — hold a TLS configuration object (yes bestie, this is the NNG Reference Manual page for it, section 3tls, we're home 🏠✨)

---

🌸 SYNOPSIS 🌸

#include <nng/nng.h>
#include <nng/supplemental/tls/tls.h>

void nng_tls_config_alloc(nng_tls_config *cfg);

ok so real talk, that synopsis is exactly what's printed on the page — nng_tls_config_alloc, not hold. Not me editing the sacred text tho 🙈 I'm just showing you what's there, character for character. 🫶

---

✨ DESCRIPTION ✨

So the whole vibe of nng_tls_config_hold() is: it bumps the reference count on the configuration object that cfg points at. Why do we care? Because that means nobody can free it while you're still using it. It's the group-chat equivalent of "don't leave yet, I'm still typing" 💅

And when you're done holding it? You let go with nng_tls_config_free(). That's the release. 🎈

Also — and this is the good part — you can stack up multiple holds on the same configuration object. It does not get freed until the last hold is released. Like, everyone has to leave the party before the lights go off, no cap. 🔥

---

🦋 RETURN VALUES 🦋

None. Zero. Nada. It gives you nothing back and honestly? That's on brand. 💀

---

🎀 ERRORS 🎀

None. Not a single one. It cannot fail you. Iconic behaviour fr fr. 👑

---

🌈 SEE ALSO 🌈

• nng_tls_config_alloc(3tls)
• nng_tls_config_free(3tls)
• nng(7)

---

and that's the whole page, bestie, go hold something 💖

this beauty lives in the NNG Reference Manual, dated 2026-06-30 — mwah, she ate, periodt ✨🎀🦋