GLOBUS_XIO_HTTP_DRIVER_SERVER(3)

🌸 NAME 🌸

globus_xio_http_driver_server — Server. that's it bestie, that's the whole name. a server. iconic. 💅

---

✨ SYNOPSIS ✨

okay so there's no function signature here, just vibes and a detailed description, so buckle up 🎀

💖 DESCRIPTION 💖

Detailed Description

Server. yes queen, we said it twice. 😌

so the way this works: calling globus_xio_server_create() makes a brand-new transport-specific listener socket get created, and its whole job is handling new HTTP connections. like, it's the bouncer at the door fr fr 🫶

then globus_xio_server_register_accept() will accept a new connection for processing. and when you're done with all that, globus_xio_server_register_close() cleans up the internal resources tied to the http server and calls close on the listener. bye bye listener, you served 💀✨

Multiple HTTP requests may be read in sequence from an HTTP server. okay so it's a line, not a one-and-done situation. after each request gets processed and the response is sent — and that response goes out either by writing the entire entity body as specified by the Content-Length header or by using the GLOBUS_XIO_HTTP_HANDLE_SET_END_OF_ENTITY handle cntl — then the next read will contain the metadata related to the next operation. slay, pipeline of dreams 🌈

⚠️ but listen: only one request will be in process at once. the previous request must have sent or received an EOF (whichever is applicable to the request type). no overlapping, no multitasking, no chaos. one at a time, periodt. 🙈

---

👑 AUTHOR 👑

Generated automatically by Doxygen for globus_xio from the source code. so it's a robot's baby, and we love it for that 🧚

---

okay bestie that's the whole page 💖 this was globus_xio Version 6.6 — mwah, stay hydrated, and remember: one request at a time, no cap 🎀🦋🌸