GLOBUS_XIO_MODE_E_DRIVER_INSTANCE(3)

✨ globus_xio_mode_e_driver_instance — the manual page, bestie edition ✨

okay so this is a page from the Library Functions Manual for globus_xio, and it's literally just about one little function, globus_xio_mode_e_driver_instance. and its whole personality? Opening/Closing. that's it. that's the vibe. 💅

---

🌸 NAME 🌸

globus_xio_mode_e_driver_instance — Opening/Closing

• Opening/Closing.

---

🦋 SYNOPSIS 🦋

Detailed Description

Opening/Closing.

---

💖 DESCRIPTION 💖

okay bestie, gather round, because this is the whole tea ☕

An XIO handle with the mode_e driver can be created with either:

• globus_xio_handle_create()
• globus_xio_server_register_accept()

so like, two doors, same room. pick your fighter. 🎀

---

If the handle is created with globus_xio_handle_create(), then the contact string you pass to the ref globus_xio_register_open() call MUST contain a host name and a service/port. no host, no port, no entry. it's giving "bouncer at the club" energy fr fr. 🚪✨

The number of streams you need can be specified on the attr using GLOBUS_XIO_MODE_E_SET_NUM_STREAMS — and heads up, the default is one stream. just the one. a solo stream. main character stream, honestly. 👑

The stack of drivers to be used on the streams can be specified on the attr using GLOBUS_XIO_MODE_E_SET_STACK — and the default there is a stack containing the TCP driver. so if you don't say anything, TCP is riding shotgun. 🚗

---

👀 and when the XIO handle is closed, the mode_e driver will destroy its internal resources and close the stream(s). it does not leave a mess. it does not leave the lights on. it cleans up and exits, iconic behaviour only. 🧹💖

---

🎀 AUTHOR 🎀

Generated automatically by Doxygen for globus_xio from the source code. not a human typing this, just a robot doing its little thing. bless. 🤖✨

---

globus_xio — Version 6.6 — and that's the whole page, bestie!! thanks for reading, mwah, go forth and open and close those handles responsibly 🫶💜🌈⭐🍓🧚

---