- Doc Structure
- A Globus Primer
- Globus Is Modular!
- Installing GT
- Platform Notes
- Migrating from GT2
- Migrating from GT3
- PDF version
- Best Practices
- Coding Guidelines
- API docs
- Public Interfaces
- Resource Properties
- Performance Studies
Table of Contents
- 1. Semantics and Syntax of XIO APIs
- 2. Semantics and Syntax of the WSDL
- 3. Semantics and Syntax of non-WSDL protocols
- 4. Command-Line Tools
- 5. Overview of Graphical User Interface
- 6. Semantics and Syntax of Domain-Specific Interface
- 7. Configuration Interface
- 8. Environment Variable Interface
Globus XIO is based on an event based asynchronous programming model. This model is described in great detail at: Asynchronous Event Handling. In short, with Globus XIO, connections are opened and closed. While open, read and write requests are posted with a callback function pointer given by the user. When the event completes, the given callback is called.
You can find documentation of the XIO library at:
For information on the internationalization API, see Section 1, “Semantics and syntax of APIs”.
This category of interfaces does not apply to XIO.
Globus XIO is a development API; therefore, configuration details are largely in the hands of the applications using it.
The vast majority of the environment variables that effect the Globus XIO framework are defined by the driver in use. The following are links to descriptions of the more common driver environment variables: