Table of Contents

CPI stands for Capability Provider Interface and it defines the interface between the SAGA runtime and adaptors (middleware plug-ins). SAGA uses a dynamic loading mechanism that allows to load adaptors during runtime to provide a specific functionality requested by the user (see http://vimeo.com/20955440). All SAGA adaptors have to be derived and conform with the CPI, otherwise the dynamic loading mechanism will fail.

The SAGA adaptor CPI provides a set of object-oriented abstract interfaces that define the structure and semantics of a SAGA adaptor. Please refer to the Adaptor Developer Documentation below for further details. The C++ class reference can be found on the left.

Adaptor Developer Documentation:

---

SAGA Adaptor Development Introduction Data Sharing Instance Data Adaptor Data Exceptions Logging Troubleshooting Bugreporting Adaptor Generator Introduction Examples CPI Package Details Advert Adaptors Filesystem Adaptors Job Adaptors Replica Adaptors RPC Adaptors SD Adaptors An Example Adaptor Generating the Stub Adaptor Adding Some Methods Compiling and Testing Licensing Things to Consider Boost Software License

Quick Class Reference Links:

---

• Advert
  • CPI Instance Data Members

• Filesystem
  • CPI Instance Data Members

• Job
  • CPI Instance Data Members