| 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
<<winmail.dat>>