GLOBUS_XIO_FILE_DRIVER_INSTANCE(3)

✨ NAME ✨

globus_xio_file_driver_instance — Opening/Closing 💖

okay bestie, this is the Opening/Closing page, like literally that's the whole vibe ✨

---

🌸 SYNOPSIS 🌸

💫 Detailed Description 💫

Opening/Closing. yes queen, that's the summary, we move 💅

So here's the tea 🍓 — you can make an XIO handle with the file driver by calling:

globus_xio_handle_create()

Now, if there's no handle set on the attr you pass into the globus_xio_open() call? It just does the equivalent of an open() call. Periodt. In that case your contact string has to contain either:

• a pathname, or
• one of stdin://, stdout://, or stderr:// 🫶

If you go with a pathname, that path gets opened, simple as. If you use one of those schemes instead, the corresponding stdio handle gets used — and it's retrieved with fileno(). iykyk 😌

Either way, the most efficient move is to call the blocking version of globus_xio_open(). Not me telling you to be efficient, it's just literally facts 📈 It's also totally safe to call inside a locked critical section, so no stress there 🔥

And when the XIO handle gets closed? The file driver destroys its internal resources and closes the fd — unless that fd was set on an attr, or it got converted from one of the stdio handles. Those ones are not it, they stay put 👑

🌈 friendly reminder that the fd situation at close time depends on where the fd came from — attr-set or stdio-converted fds are the exception, no cap.

---

👑 Author 👑

Generated automatically by Doxygen for globus_xio from the source code. iconic behaviour honestly, the robots did that 💖

---

and that's the whole page bestie, mwah 🎀

signing off from globus_xio Version 6.6, manual section 3 — stay slay, drink water, close your fds 🦋✨