You can think this way:
domainURI: The URI of an SCA domain is the "logical id" (or name) of the
domain. The syntax of the URI is free-form and it doesn't imply any URL
connections.
domainRegistryURI: The URI of the "physical address" for the domain
registry. For example, we can use "tribes://228.0.0.100:50000" to say we are
going to use a tribes-based multicast over 228.0.0.100 (a multicast address
for the group) and port 50000. If the domain registry is a HTTP based
server, then the URI can be something like http://myhost:8080/mydomain.
Theoretically, we can use the same protocol address to support multiple SCA
domains. The domain URI can then be used to organize the entries for
endpoint descriptions.
Thanks,
Raymond
--------------------------------------------------
From: "Simon Laws" <[email protected]>
Sent: Tuesday, December 08, 2009 9:59 AM
To: <[email protected]>
Subject: Re: [2.x] node configuration attributes
ok, wasn't suggesting that we remove node/@uri just questioning it's
name. So we would have...
<node xmlns:sca="http://docs.oasis-open.org/ns/opencsa/sca/200903";
xmlns="http://tuscany.apache.org/xmlns/sca/1.1";
xmlns:tuscany="http://tuscany.apache.org/xmlns/sca/1.1";
uri="http://sample/nodes/TestNode1";
domainURI="http://domain1";
domainRegistryURI="tribes:default">
Still not clear about the precise utility of domainURI vs
domainRegistryURI. I'll take a look at the code
Simon
