Content deleted Content added
Line 15:
The SAGA [[API]] does not strive to replace [[Globus_Toolkit|Globus]] or similar [[grid computing]] middleware systems, and does not target middleware developers, but application developers with no background on grid computing. Such developers typically wish to devote their time to their own goals and minimize the time spent coding infrastructure functionality. The API insulates application developers from middleware.
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. A large part of the SAGA Core API specification
== Standardization ==
| |||