Difference between revisions of "Integration and Interoperability Facilities Framework: Client Libraries"

From Gcube Wiki
Jump to: navigation, search
(→‎Client Libraries)
(→‎Design Model)
Line 11: Line 11:
 
== Design Model ==
 
== Design Model ==
  
−
The '''design model''' for client libraries identifies a core set of capabilities that all libraries ought to offer, independently from the specific semantics for target services and the technologies required to interact with those services. Furthermore, the model defines common design recipes for client libraries, all of which are based on established best practices and are motivated by goals of simplicity, testability, evolvability and, where appropriate, compliance with standards.  These include:
+
The '''design model''' for client libraries identifies a core set of capabilities that all libraries are required to offer, regardless of the specific semantics of target services and the client-side technologies required to interact with those services. The model defines also common design patterns for client libraries, where the patterns are based on best practices and are motivated by goals of simplicity, testability, evolvability and standards compliance.  Topics that fall within the scope of model include:
  
−
* the management of service endpoints, including endpoint discovery through queries, endpoint binding strategies, and endpoint address caching strategies;
+
* the local model of service endpoints;
−
* the management of faults thrown by service endpoints, including fault classification and modelling within the language;
+
* the discovery of service endpoints;
−
* the management of call scope and client credentials;
+
* the fault-tolerant binding to service endpoint replicas;
−
* the support for asynchronous interactions, including interactions based on polling, notifications, or data streams;
+
* the caching of service endpoints addresses across interactions;
−
* the design of state-related operations;
+
* the classification, modelling, and handling of interaction failures;
 +
* the handling of call scope and client credentials;
 +
* the design of asynchronous interactions, including interactions based on polling, notifications, and data streams;
  
 
Read more about the design model for client libraries [[Integration_and_Interoperability_Facilities_Framework:_Client_Libraries_Design_Model|here]].
 
Read more about the design model for client libraries [[Integration_and_Interoperability_Facilities_Framework:_Client_Libraries_Design_Model|here]].

Revision as of 22:17, 21 May 2012

Client Libraries

The CL layer of the Integration and Interoperability Framework focuses on the design, implementation, and management of client libraries, i.e. system components that mediate access to system services from within client Java runtimes.

In particular, the layer defines:

  • a design model that codifies approaches to design issues which are common to all client libraries;
  • an implementation framework that provides the support required to implement client libraries which comply with the design model;
  • a management model that identifies technologies and best practices for client library management, including testing, building, and distribution;

Design Model

The design model for client libraries identifies a core set of capabilities that all libraries are required to offer, regardless of the specific semantics of target services and the client-side technologies required to interact with those services. The model defines also common design patterns for client libraries, where the patterns are based on best practices and are motivated by goals of simplicity, testability, evolvability and standards compliance. Topics that fall within the scope of model include:

  • the local model of service endpoints;
  • the discovery of service endpoints;
  • the fault-tolerant binding to service endpoint replicas;
  • the caching of service endpoints addresses across interactions;
  • the classification, modelling, and handling of interaction failures;
  • the handling of call scope and client credentials;
  • the design of asynchronous interactions, including interactions based on polling, notifications, and data streams;

Read more about the design model for client libraries here.

Implementation Framework

The design model for client libraries identifies capabilities and patterns common to all libraries, but it does not specify how libraries provide those capabilities or implement those patterns, nor does it mandate low-level details of their interfaces.

The client library framework is a tool for the development of client libraries that comply with the model. Through code sharing, the framework reduces development costs and ensures the consistency and correctness of library implementations.

Read more about the client library framework here.

Management Model

Management Model: The model for CL management will address at least the following (inter-related) issues:

  • module structure: relationship between CL modules, stub modules, and service modules
  • build outputs: what secondary artifacts are associated with CLs
  • release cycle: how are CLs released with respect to target services
  • change management: how changes in target service API should be handled
  • profiling and deployment: how should CLs be profiled for dynamic deployment
  • distribution: how should CLs be packaged for distribution
Retrieved from "https://wiki.gcube-system.org/index.php?title=Integration_and_Interoperability_Facilities_Framework:_Client_Libraries&oldid=14851"