| RE: [cosmos-dev] Client API ERhttp://wiki.eclipse.org/COSMOS_Design_197870 |
|
Jimmy Each
component (Data Broker, Data Manager, etc) has a corresponding set of Client
API convenience methods. I agree with Hubert’s suggestion to move each
set of Client API convenience methods to its respective component. I have already
moved the Data Broker Client API to the Data Broker design page and I’m
planning on moving the Data Manager Client API convenience methods to the Data
Manager design page next. Accordingly,
I think the Client API for the Management Domain belongs in the Manager Domain
design page. The result is that the Client
API ER should be closed because it will be consumed by the component ERs. Regards Bill From:
cosmos-dev-bounces@xxxxxxxxxxx [mailto:cosmos-dev-bounces@xxxxxxxxxxx] On Behalf Of Mohsin, Jimmy Bill, The Client API ER (http://wiki.eclipse.org/COSMOS_Design_197870)
refers to the following: 1. In the “Purpose”
section, the design states “The Client API contains convenience methods for the
client application to use to access the Data Broker and Data Managers.” 2. In the “Use Case
section”, the design captures “Use case 1: access the Data
Broker using the Client API. Use case 2: access a Data Manager
using the Client API.” Should the client API design include considerations for the
Management Domain AS WELL ??? Or should this be an i6 item? Thanks, Jimmy Mohsin +1-609-635-1703 |