GLOBUS_XIO_MODE_E_DRIVER_IO(3)

πŸ“¦
version 6.6 Β· 5 versions
, in epel 10, fedora 43, fedora 44, ubuntu resolute, ubuntu stonking

✨ NAME ✨

globus_xio_mode_e_driver_io β€” Reading/Writing πŸ’–

okay so bestie, this whole thing is literally about Reading/Writing. that's the vibe. that's the whole assignment. πŸŽ€


✨ SYNOPSIS ✨

(no synopsis line here, just the deets below, keep scrolling queen πŸ‘‘)


✨ Detailed Description ✨

Reading/Writing. πŸ¦‹

okay so here's the tea: Mode E is unidirectional. that means it only goes one way, no back-and-forth, no take-backs. Clients can only write and the server can only read. that's it, that's the dynamic, and honestly? it's giving very one-sided texting energy πŸ’€

globus_xio_register_read() enforces that the waitforbytes parameter should be one. like, one. exactly one. not two, not zero, one. it's very strict about this, no cap. 🫢

and when multiple transport streams are used between the client and the server, data might not be delivered in order. yeah. it can show up out of sequence, which is lowkey chaotic but also iconic in its own way. so if you need to know where your data actually landed, you can use globus_xio_data_descriptor_cntl() to get the offset of the data. problem solved, slay. ✨

meanwhile globus_xio_register_write() does not enforce any restriction on the waitforbytes parameter. it's the chill one. the go-with-the-flow one. the main character who doesn't do rules. πŸ’…

and in any case β€” listen up, this part matters, fr fr β€” when an error or EOF occurs before the waitforbytes request has been met, the outgoing nbytes is set to the amount of data actually read/written before the error or EOF occurred. so like, you don't get the full number you asked for, you get the real number of what made it through. no inflation, no pretending, just the honest count. 🌸

ngl bestie, remember: error or EOF mid-request = nbytes reflects what actually got read/written. not what you wanted. what you got. πŸ’œ

✨ Author ✨

Generated automatically by Doxygen for globus_xio from the source code. so technically a robot wrote this and i'm just the messenger, don't shoot me πŸ™ˆ


and that's the whole page, bestie!! πŸŽ€ this was globus_xio Version 6.6, straight from the globus_xio manual, page globus_xio_mode_e_driver_io(3). go forth and write on the client side, read on the server side, and stay unidirectional πŸ’–βœ¨πŸ¦‹πŸ’…

πŸ“¦ where this page comes from