GLOBUS_NET_MANAGER_ATTR_S(3)

πŸ“¦
version 1.7 Β· 6 versions
, in fedora 43, fedora 44, ubuntu resolute, ubuntu stonking

✨ NAME ✨

globus_net_manager_attr_s β€” Net Manager Attributes, bestie πŸ’–

(also chillin' in the Library Functions Manual section of the manual, iykyk)


🌸 SYNOPSIS 🌸

#include <globus_net_manager_attr.h>

πŸŽ€ Data Fields

  • char * scope
  • char * name
  • char * value

πŸ¦‹ Detailed Description πŸ¦‹

okay so. Net Manager Attributes. let me put you on.

The globus_net_manager_attr_t structure defines a scoped (attribute, value) tuple. that's it, that's the whole vibe β€” a little pair of things, but with scope attached, like a group chat where every message knows which room it's in πŸ’…

and the scope? in most cases it's either:

  • the name of the transport driver, or
  • the "globus_net_manager" scope β€” which is where the attributes specific to the network manager implementation live

so basically the scope is the "which chat is this" label and the attribute/value is the actual message. iconic honestly πŸ‘‘


🧚 Field Documentation 🧚

πŸ’œ char* globus_net_manager_attr_s::name

Name of the attribute. that's the what β€” the label on the thing ✨

πŸ’œ char* globus_net_manager_attr_s::scope

Scope of the attribute. that's the where it belongs β€” which driver or which "globus_net_manager" world it's chillin' in 🌈

πŸ’œ char* globus_net_manager_attr_s::value

Value of the attribute. that's the actual content, the payload, the main character of the trio fr fr 🫢


πŸ‘‘ Author πŸ‘‘

Generated automatically by Doxygen for globus_net_manager from the source code. not a human writing this by hand, just Doxygen doing its little automated slay πŸ€–βœ¨


ngl bestie, this whole page is autogenerated, so if something's giving weird, blame the doc generator, not me πŸ’€

Version 1.7 of globus_net_manager, and the manual name is Library Functions Manual β€” that's the sign-off, mwah, go forth and scope your attributes properly πŸŽ€πŸ’–

πŸ“¦ where this page comes from