Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cosmos-dev] RE: [YAJQ] What drives the overall interactions between the Broker, Management Domain, Data Managers

Mark,

 

I have added a section at the end of the talk page:

http://wiki.eclipse.org/Talk:COSMOS_Design_197870

 

All,

Please comment liberally; we need to really determine the nature / “responsibilities” of the component we have been calling the “Client API”. The MORE I think about it, the more convinced I get that it will have some sort of management capabilities (in addition to being called by a client).

 

Thanks,

Jimmy Mohsin

+1-609-635-1703


From: Mark D Weitzel [mailto:weitzelm@xxxxxxxxxx]
Sent: Monday, August 20, 2007 9:30 AM
To: Simmonds, Martin; Mohsin, Jimmy
Subject: Fw: [cosmos-dev] What drives the overall interactions between theBroker, Management Domain, Data Managers

 


Martin/Jimmy,

Would you be kind enough to update the wiki page for the design with the thread below?
http://wiki.eclipse.org/COSMOS_Design_197870
 
Thanks!

-mw
_______________________________________________________________________________________________________________
Mark Weitzel | STSM | IBM Software Group | Tivoli | Autonomic Computing | (919) 543 0625 | weitzelm@xxxxxxxxxx

----- Forwarded by Mark D Weitzel/Raleigh/IBM on 08/20/07 09:27 AM -----

"Simmonds, Martin" <Martin.Simmonds@xxxxxx>
Sent by: cosmos-dev-bounces@xxxxxxxxxxx

08/19/07 05:28 PM

Please respond to
Cosmos Dev <cosmos-dev@xxxxxxxxxxx>

To

"Cosmos Dev" <cosmos-dev@xxxxxxxxxxx>

cc

 

Subject

RE: [cosmos-dev] What drives the overall interactions between        theBroker, Management Domain, Data Managers

 

 

 




Hi,

The client API has to have some intelligence. After all, once it finds out from the management domain where the broker is, it starts to do its own stuff anyway.  If that intelligence was shifted elsewhere, the client would have to understand that also. The problem is that the client could do any number of things when it knows where the broker is, or when it knows where the Data Managers are.

Martin...




-----Original Message-----
From: cosmos-dev-bounces@xxxxxxxxxxx on behalf of Mohsin, Jimmy
Sent: Sun 8/19/2007 9:32 PM
To: Cosmos Dev
Subject: [cosmos-dev] What drives the overall interactions between theBroker, Management Domain, Data Managers

All,



Something I was thinking about as part of our design.  Is there a COSMOS
component that plays the role of a "conductor"?



As a start, please review the attached picture. In this, it is apparent
that the Client API "knows" about ALL the COSMOS components.
Specifically, the client API communicates with the Management Domain,
the Broker, and the Data Manager.  The client ALSO needs to be aware of
the SEQUENCE in which it communicates with the various components.  Does
this mean that the client API is playing the role of a (perhaps)
conductor  / low end workflow manager?



Thanks,

Jimmy Mohsin

+1-609-635-1703




_______________________________________________
cosmos-dev mailing list
cosmos-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cosmos-dev


Back to the top