event_proxy(4gx)

🦋 event_proxy — Event sender 🦋

okay so this is the event_proxy(4gx) page from the Gromox admin reference, and bestie, it's literally the event sender. no cap. ✨

🎀 Name 🎀

event_proxy — Event sender. That's the whole title, and honestly? it ate. 💅

🌈 Description 🌈

event_proxy connects to the event(8gx) daemon and sets itself up so as to be able to send notifications. It's giving "ready to slide into event distribution's DMs," fr fr. 🫶

event_proxy installs three service functions: broadcast_event, broadcast_select and broadcast_unselect. The latter two are just convenience functions for broadcast_event — like, they're the supporting cast, and broadcast_event is the main character. 👑

broadcast_event is for synchronously sending a notification into the event distribution system. Arbitrary notifications and commands can be sent this way. The return value (i.e. in the eventd network protocol) is ignored. Not me expecting a reply... the return value is literally ignored, periodt. 💀

In practice, midb(8gx), imap(8gx) and pop3(8gx) issue FOLDER-TOUCH notifications. Only imap(8gx) issues MESSAGE-FLAG and MESSAGE-EXPUNGE notifications. So imap(8gx) is out here doing the absolute most, and we're obsessed. 🔥

🫶 See also 🫶

• event(8gx)
• event_stub(4gx)

✨ sign-off time: source/version is Gromox, the page is event_proxy(4gx), and the footer date is not shown here, bestie — that's the whole footer vibe 💖