From:
cosmos-dev-bounces@xxxxxxxxxxx [mailto:cosmos-dev-bounces@xxxxxxxxxxx] On Behalf Of Hubert H Leung
Sent: Wednesday, July 18, 2007 11:41 AM
To: Cosmos Dev
Subject: RE: [cosmos-dev] question
on management domain and brokers
I remember Martin said in the meeting that data
managers contact the management domain, not a broker. The management
domain has a UDDI registry, which is a logical place to start to discover
location of brokers. If data managers know how to contact brokers
directly, the clients can do that as well. Then what's the use of the
management domain? (I could be wrong. That's why I asked for a
sequence diagram.) What I'm trying to clarify is not the "merged
domain manager / broker" simplified scenario, but the real multi-broker
scenario. "Visit all brokers until you find one that works" is not an
elegant solution. This is essentially a question about how to manage data
providers and how to access data in the COSMOS system management environment.
Regards,
_________________________
Hubert Leung
IBM Toronto Lab
hkyleung@xxxxxxxxxx
905-413-3382
"Hawkins, Joel"
<Joel.Hawkins@xxxxxxxxxxxxx>
Sent
by: cosmos-dev-bounces@xxxxxxxxxxx
07/18/2007 11:13 AM
Please
respond to
Cosmos Dev <cosmos-dev@xxxxxxxxxxx>
|
|
To
|
"Cosmos Dev"
<cosmos-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
|
RE: [cosmos-dev] question on management
domain and brokers
|
|
Hi Hubert,
Hi all,
I have a follow up question on the use of management domain and brokers from
yesterday's DC meeting. If we consider using a management domain with
multiple brokers, what logic/algorithm will be used to route a client request
to the appropriate broker (assuming the brokers aren't redundant copies of each
other)? Similarly, when data manager contacts a management domain at
startup, how does the management domain decide which broker it belongs to?
My understanding is that
the DataManager contacts its DataBroker, and the DomainManager only knows about
DataBrokers . The nice thing about this is we can easily support the ‘No
DomainManager’ simplified scenario. We can support routing either
naively (basically visiting each know DataBroker until we get one that works
for a particular request), or we can route based on prior knowledge (sticky
sessions and/or routing based on cached information about similar request).
This could be a place for ‘value-add’.
Also, when Martin writes up the notes on how the management domain works, it
would be useful if he can provide a sequence diagram or equivalent on the steps
and any handshaking protocols of the bootstrap process and the request handling
process.
Good idea.
Thanks,
The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose it
to anyone else. If you received it in error please notify us immediately and
then destroy it.
Hubert Leung
IBM Toronto Lab
hkyleung@xxxxxxxxxx
905-413-3382
_______________________________________________
cosmos-dev mailing list
cosmos-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cosmos-dev