globus_callout(3)

💖 globus_callout — the Globus Callout API, bestie edition

okay so this is globus_callout(3), from the Library Functions Manual, and it's literally the Globus Callout API. Buckle up, we're doing configurable callouts and runtime loadable functions and it's gonna be a whole vibe. 🦋

---

✨ NAME ✨

globus_callout — the Globus Callout API.

(yeah that's it, that's the name, and also, again: the Globus Callout API. iconic of it to say it twice. 💅)

---

✨ SYNOPSIS ✨

🎀 Topics

So the docs are organized into little topic clusters, and here's the full lineup:

• Activation — Callback API Activation.
• Callout Handle Operations — Manage a Globus Callout Handle structure.
• Callout Configuration — Register callouts.
• Callout Invocation — Invoke callouts.
• Callout Constants — Constants.

---

🌸 Detailed Description 🌸

Globus Callout API. 💖

Bestie, listen. This API exists to make it easy to plug configurable callouts into the Grid Community Toolkit, and to give you a platform independent way of dealing with runtime loadable functions. That's the whole mission statement. And (hopefully — their words, not mine, they said "hopefully", I'm cryin 😭) it pulls this off by handing you the following:

• It gives you a function for reading callout configuration files. And those files are assumed to look like this:
  • Anything after a # is assumed to be a comment.
  • Blank lines are ignored.
  • Lines that specify callouts have the format:

abstract type           library         symbol

• where abstract type denotes the type of callout, e.g. globus_gram_jobmanager_authz, library denotes the library the callout can be found in, and symbol denotes the function name of the callout.

• It gives you an API function for registering callouts. 🫶
• All callouts are assumed to have this function signature:

globus_result_t callout_func(va_list ap)

• It gives you a function for calling a callout given an abstract type. And here's the tea: if multiple callouts are defined for the same abstract type, then all the callouts for that abstract type will be called. Also, implementers should not rely on any correlation between the order of configuration and the order of invocation of callouts of the same abstract type. So like, don't assume the config order is the call order. It is not. periodt. 💀

Any program that uses Globus Callout functions must include the globus_callout.h header.

---

👑 Function Categories

• Activation
• Callout Handle Operations
• Callout Configuration
• Callout Invocation
• Callout Constants

---

🧚 Author 🧚

Generated automatically by Doxygen for globus_callout from the source code. (not a girlboss human, a girlboss robot ✨)

---

and that's the whole page, no cap. this was globus_callout, Version 4.3, from the globus_callout(3) manual — slay, go write some callouts bestie 💜🌈