globus_xio...ver_server(3)

🌸 NAME 🌸

globus_xio_tcp_driver_server — bestie, it's the Server. That's it, that's the whole thing. Server. 💅

This one lives in the globus_xio section 3 manual (Library Functions Manual), so like, yes, it's a library function page, not a command you run in your shell. iykyk 🦋

---

✨ SYNOPSIS ✨

okay so this page is <em>mostly</em> a description page, no big fancy argument list, no flags to memorise, none of that. We're just vibing with the tcp driver's server-side story. 🎀

📖 Detailed Description 📖

Server. 🫶

No fr, let's get into it, because the tcp server side is actually doing a lot of behind-the-scenes work:

• globus_xio_server_create() — the way that this one is literally the moment a tcp listener socket gets created and listened upon. Like, the socket is up, it's listening, it's in its main character era. 👑
• globus_xio_server_register_accept() — this is what performs an asynchronous accept(). Asynchronous! Not me waiting around blocking, we're doing it async, slay. ✨
• globus_xio_server_register_close() — the cleanup queen 🧹. This one cleans up the internal resources associated with the tcp server, and it calls close() on the listener socket — unless the socket was set on the server via the attr. (so like, if you handed it your own socket through the attr, it's not gonna yank it out from under you, okay? noted. 💜)

🫶 also important, bestie: all accepted handles inherit all the tcp specific attributes that were set in the attr passed to globus_xio_server_create(). But (and this is the good part) you can totally override them with the attr you pass to globus_xio_register_open(). Inherit, then override. It's giving flexible. 🌈

---

👑 Author 👑

Generated automatically by Doxygen for globus_xio from the source code. So like, don't @ me, @ Doxygen, it wrote itself fr fr. 😭

---

and that's the page, babe 🎀 globus_xio, Version 6.6, coming at you from the globus_xio manual. Go build a server, you've got this. 💖 🦋 ✨