radcli_dae_set_handler(3)

πŸ“¦ version 2.0.1, in arch rolling

πŸ’… radcli_dae_set_handler β€” bestie's guide to hooking up your DAE callback πŸ’–

So this is a page from the radcli crew β€” the Radius client library, hi β€” and it's about radcli_dae_set_handler, which registers the callback that radcli_ctx_dispatch() invokes for each validated request. And the slay part? You can call it before or after radcli_dae_start(). No cap, it's flexible like that. ✨


✨ SYNOPSIS ✨

#include <radcli/>

void radcli_dae_set_handler(
    radcli_dae        *dae,
    radcli_dae_handler cb,
    void              *user
);

πŸŽ€ DESCRIPTION πŸŽ€

Okay so like… the original page has this heading sitting here with absolutely nothing under it 😭 literally an empty vibe. So we're not gonna invent anything β€” we just move straight to the parameters, iykyk. 🫢


🌸 PARAMETERS 🌸

  • dae β€” a listener that came from radcli_dae_new(). Your main character listener, if you will πŸ‘‘
  • cb β€” the callback itself πŸ’… and heads up: pass NULL if you wanna clear a previously registered one. Poof, gone, iconic.
  • user β€” just gets passed right back to cb unchanged. No edits, no notes, no nothing β€” it comes back exactly how it left. πŸ¦‹

πŸ”₯ SEE ALSO πŸ”₯

Go read these next, fr fr β€” they're all the siblings and they all ate:


Bestie reminder: cb being NULL isn't a bug, it's a feature β€” it's how you clear the handler you set earlier. Don't @ me. πŸ’€

Okay that's the whole page, you're all caught up πŸ§šπŸ’œ this was radcli, dated 2026-10-10, and we are so done here β€” mwah! πŸŽ€πŸŒˆβ­

πŸ“¦ where this page comes from