GLOBUS_I_FTP_CLIENT_CACHE_ENTRY_T(3)

📦
version 9.9 · 7 versions
, in fedora 44, ubuntu resolute, ubuntu stonking

💖 NAME 💖

globus_i_ftp_client_cache_entry_t — the URL caching support structure, bestie 💅 (this page lives in the Library Functions Manual, in case you were wondering 🎀)

✨ SYNOPSIS ✨

#include <globus_i_ftp_client.h>

🌸 Data Fields 🌸

  • globus_url_t url
  • globus_i_ftp_client_target_t * target

🦋 Detailed Description 🦋

okay so. globus_i_ftp_client_cache_entry_t is literally the URL caching support structure. That's the whole vibe. 🫶

Here's the tea: this structure is what implements the cache of URLs. When a target is needed, the client library first checks the handle's cache. And if the target associated with the url is available, and it matches the security attributes of the operation being performed, then it gets used for the operation. no cap. 🔥

not me being dramatic but the current implementation only allows for a URL to be cached only once per handle. that's the limit, periodt. 🙈

The cache manipulations are done by the API functions globus_ftp_client_cache_url_state() and globus_ftp_client_flush_url_state(), plus the internal functions globus_i_ftp_client_target_find() and globus_i_ftp_client_target_release(). iykyk. ✨

🌈 Field Documentation 🌈

💜 globus_i_ftp_client_target_t* globus_i_ftp_client_cache_entry_t::target

The target which matches that URL. And if this is NULL? then the cache entry is empty. it's giving nothing left to give 💀

💜 globus_url_t globus_i_ftp_client_cache_entry_t::url

The URL which the user has requested to be cached. iconic, honestly 👑

👑 Author 👑

Generated automatically by Doxygen for globus_ftp_client from the source code. (yes, a robot wrote this, and it ate 🎀)

and that's a wrap on globus_i_f...che_entry_t(3) from globus_ftp_client, Version 9.9 🦋 stay cached, stay slay, mwah 💖

📦 where this page comes from