Difference between revisions of "Integration and Interoperability Facilities Framework: Client Libraries Framework"
(Created page with ' gCube includes client libraries for many of its services and defines a [[https://gcube.wiki.gcube-system.org/gcube/index.php/Integration_and_Interoperability_Facilities_Framewor…') |
|||
| Line 1: | Line 1: | ||
| − | + | gCube includes client libraries for many of its services and defines a [[Integration_and_Interoperability_Facilities_Framework:_Client_Libraries_Design_Model|general model]] for their design. The model requires that, regardless of specific service semantics and client-side technology stacks, all libraries support a common set of capabilities and adopt the same solutions to design issues that recur across their client interfaces. | |
| − | gCube includes client libraries for many of its services and defines a [[ | + | |
However, the model does not specify how libraries are implemented to provide such capabilities and design solutions, nor does it mandate the low-level details of their APIs. | However, the model does not specify how libraries are implemented to provide such capabilities and design solutions, nor does it mandate the low-level details of their APIs. | ||
The '''client library framework''' is a set of components that support the development of client libraries which comply with the model. Through code sharing, the framework reduces development costs and ensures the consistency and correctness of library implementations. | The '''client library framework''' is a set of components that support the development of client libraries which comply with the model. Through code sharing, the framework reduces development costs and ensures the consistency and correctness of library implementations. | ||
| − | In this | + | In this document, we illustrate how the framework can be used to develop a client library for a hypothetical <code>foo</code> service. |
| − | + | ||
= Distribution = | = Distribution = | ||
= Overview = | = Overview = | ||
| − | |||
| − | |||
| − | |||
| − | |||
= Calls and Delegates = | = Calls and Delegates = | ||
Revision as of 23:30, 21 May 2012
gCube includes client libraries for many of its services and defines a general model for their design. The model requires that, regardless of specific service semantics and client-side technology stacks, all libraries support a common set of capabilities and adopt the same solutions to design issues that recur across their client interfaces.
However, the model does not specify how libraries are implemented to provide such capabilities and design solutions, nor does it mandate the low-level details of their APIs. The client library framework is a set of components that support the development of client libraries which comply with the model. Through code sharing, the framework reduces development costs and ensures the consistency and correctness of library implementations.
In this document, we illustrate how the framework can be used to develop a client library for a hypothetical foo service.
