NNG_DIALER_START(3)

💅 NNG_DIALER_START(3) — the nng_dialer_start manual, bestie edition 🎀

okay so this is the page for nng_dialer_start, straight out of the NNG Reference Manual. it's a little three-parter: you got a dialer, you got flags, and you got ✨vibes✨ (the vibes being "please connect to somebody"). let's get into it 🦋

---

🌸 NAME 🌸

nng_dialer_start — start that dialer, no cap

---

✨ SYNOPSIS ✨

#include <nng/nng.h>

int nng_dialer_start(nng_dialer d, int flags);

---

💖 DESCRIPTION 💖

so nng_dialer_start() literally just starts the dialer d. that's it, that's the function 💅

what "start" means here: it makes the dialer begin connecting to the address it was created with. like, the dialer has been sitting there with an address in its pocket this whole time and now we're finally letting it go do the thing 🫶

and when a connection actually gets established? that results in a pipe being created, and that pipe gets attached to the dialer's socket. so cute. so functional. 🌈

okay now the important part, so listen up bestie 👑

normally, the first attempt to connect to the dialer's address happens synchronously, and that includes any name resolution it needs. which means: if that first try fails — say the connection gets refused — the failure comes back to you immediately, and no further action will be taken. like, it just stops. that's it. done. 💀

BUT. if you pass the special value NNG_FLAG_NONBLOCK in flags, then the connection attempt gets made asynchronously instead. slay ✨

also lowkey important: if the connection was closed for a synchronously dialed connection, the dialer will still attempt to redial asynchronously. it does not give up, it is giving main character energy 🔥

🌟 Tip NNG_FLAG_NONBLOCK can genuinely help your application be more resilient, but it also generally makes diagnosing failures somewhat more difficult. so like… tradeoffs, bestie. pick your struggle 😭

and one more thing, because it matters: once a dialer has started, it is generally not possible to change its configuration. the dialer has made its choices and it's committing to them. periodt. 🔒

---

🫶 RETURN VALUES 🫶

this function returns 0 on success, and non-zero otherwise. that's the whole deal 💖

---

💀 ERRORS 💀

here's the full menu of things that can go wrong, no skipping, we list them all:

• NNG_EADDRINVAL — an invalid url was specified. bad address, babe 🙈
• NNG_ECLOSED — the socket s is not open.
• NNG_ECONNREFUSED — the remote peer refused the connection. rude tbh 😤
• NNG_ECONNRESET — the remote peer reset the connection. also rude!!
• NNG_EINVAL — an invalid set of flags was specified. your flags did not pass the vibe check 🚩
• NNG_ENOMEM — insufficient memory is available. we are out of brain cells (RAM) 😭
• NNG_EPEERAUTH — authentication or authorization failure. you shall not pass 🔐
• NNG_EPROTO — a protocol error occurred. the protocols are fighting 💥
• NNG_ESTATE — the dialer d is already started. bestie it's already doing the thing, calm down 💅
• NNG_EUNREACHABLE — the remote address is not reachable. it's not you, it's the network 🦋

---

⭐ SEE ALSO ⭐

nng_dial(3), nng_dialer_create(3) nng_strerror(3), nng_dialer(5), nng(7)

go read those too, iykyk 📚

---

and that's the whole page, bestie!! 🎀 this one's from the NNG Reference Manual, dated 2026-06-30, and it was NNG_DIALER_START(3) all along 👑 ok bye, go start a dialer, love u 💜🌸✨