globus_i_f...ndleattr_t(3)
π globus_i_f...ndleattr_t(3) π
okay bestie, welcome to the Library Functions Manual section, and yes the title got squished to globus_i_f...ndleattr_t(3) because somebody at the top of the page said "how much name do you need" and the answer was apparently "not that much". Anyway. Sit down, hydrate, we're learning about handle attributes today. π«Ά
β¨ NAME β¨
globus_i_ftp_client_handleattr_t β Handle attributes. That's the whole name, that's the whole vibe, it's giving "struct with opinions". π
πΈ SYNOPSIS πΈ
#include <globus_i_ftp_client.h>
π Data Fields
globus_bool_t cache_allglobus_bool_t rfc1738_urlglobus_bool_t gridftp2globus_list_t * url_cacheglobus_list_t * plugins
π¦ Detailed Description π¦
Handle attributes. That's it. That's the description. It's short, it's sweet, it's lowkey the whole point of the page. β¨
π Field Documentation π
π globus_bool_t globus_i_ftp_client_handleattr_t::cache_all
Cache all connections.
This attribute is what you flip on to make the ftp client library keep all control connections open between ftp operations β and, where possible, the data connections too. Not me turning on cache_all and never looking back π it's literally just "keep the connections, bestie, don't ghost them".
π globus_bool_t globus_i_ftp_client_handleattr_t::gridftp2
Use GRIDFTP2 if supported by the server
That's it, that's the field. It says what it does. If the server supports it, GRIDFTP2 gets used. If notβ¦ well. It's conditional, babes, it's giving "if they're ready for it". π
π§ globus_list_t* globus_i_ftp_client_handleattr_t::plugins
List of plugin structures.
This list contains all plugins which can be associated with an ftp client handle. These plugins will be notified when operations are done using a handle associated with them.
So like, the group chat of plugins. Every time an operation goes down on a handle that's linked to them, they all get the notification. periodt. π₯
π globus_bool_t globus_i_ftp_client_handleattr_t::rfc1738_url
parse all URLs for caching with RFC1738 compliant parser
Yep, all of them. Every single URL gets run through the RFC1738 compliant parser for caching purposes. No shortcuts, no vibes-based parsing, the standard said what it said. π
β globus_list_t* globus_i_ftp_client_handleattr_t::url_cache
List of cached URLs.
This list is used to manage the URL cache, which is manipulated by the user calling globus_ftp_client_handle_cache_url_state() and globus_ftp_client_handle_flush_url_state().
So the cache is real, it lives here, and you drive it with those two functions. iykyk. π«
πΈ Author πΈ
Generated automatically by Doxygen for globus_ftp_client from the source code. Not a human, not a bestie, just Doxygen doing its little robot thing. π€β¨
and that's the whole page, bestie!! π this was globus_ftp_client Version 9.9, straight from the globus_ftp_client manual, and the footer was living its best life as globus_i_f...ndleattr_t(3) on the right-hand side. slay, go cache some URLs, love u ππ¦π
π¦ where this page comes from
- epel 10: globus-ftp-client-doc 9.9-1.el10_2 Β· Apache-2.0
- fedora 43: globus-ftp-client-doc 9.9-1.fc43 Β· Apache-2.0
- fedora 44: globus-ftp-client-doc 9.9-2.fc44 Β· Apache-2.0
- ubuntu resolute: libglobus-ftp-client-doc 9.9-1 Β· Apache-2.0
- ubuntu stonking: libglobus-ftp-client-doc 9.9-2build1 Β· Apache-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms