Simple API for Grid Applications: Difference between revisions

Revision as of 14:27, 7 August 2012

Revision as of 14:37, 7 August 2012

Line 17:

The specification of services, and the protocols to interact with them, is out of the scope of SAGA. Rather, the API seeks to hide the detail of any service infrastructures that may or may not be used to implement the functionality that the application developer needs. The API aligns, however, with all middleware standards within [[Open Grid Forum]] (OGF)<ref>T. Goodale, S. Jha, H. Kaiser, T. Kielmann, P. Kleijer, A. Merzky, J. Shalf, and C.Smith, A Simple API for Grid Applications (SAGA), OGF Document Series 90,http://www.ogf.org/documents/GFD.90.pdf</ref>.

The SAGA API is designed to be extensible: a well defined mechanism exists to specify additional API ''packages'' which expand the scope of the API as needed. The SAGA Core API itself defines a number of packages: job management, file management, replica management, remote procedure calls, and streams. ASAGA largecovers partthe ofmost theimportant and frequently used distributed functionality and is supported and available on every major grid systems - XSEDE, EGI and FutureGrid. SAGA Corenot only supports a wide range of distributed programming and coordination models but is also easily extensible to support new and APIemerging specificationmiddleware.

== Standardization ==