globus_callout - Globus Callout API
- Globus Callout API.
Activation
Callback API Activation. Callout Handle Operations
Manage a Globus Callout Handle structure. Callout Configuration
Register callouts. Callout Invocation
Invoke callouts. Callout Constants
Constants.
Globus Callout API.
This API is intended to ease integration of configurable callouts
into the Grid Community Toolkit and to provide a platform independent way of
dealing with runtime loadable functions. It (hopefully) achieves this goal
by providing the following functionality:
- •
- It provides a function for reading callout configuration files. Files are
assumed to have the following format:
- •
- Anything after a # is assumed to be a comment
- •
- Blanks lines are ignored
- •
- Lines specifying 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 provides a API function for registering callouts
- All callouts are assumed to have the function signature globus_result_t
callout_func(va_list ap)
- It provides a function for calling a callout given an abstract type. If
multiple callouts are defined for the same abstract type then all callouts
for the abstract type will be called. Implementers should not rely on any
correlation between the order of configuration and the order of invocation
of callouts of the same abstract type.
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
Generated automatically by Doxygen for globus_callout from the
source code.