On Thu, Jan 14, 2010 at 9:05 AM, Simon Laws <[email protected]> wrote: > Working out what the question is before offering an opinion.... > > Firstly there seems to be a few overlapping things here. There is is > the information itself > > The unique identifier of a domain
Yes > Whether this domain is a tuscany: runtime domain or a domain provided > by some other domain Thats not actually supported by the current OASIS code, i do have a memory that was intended to be support but maybe the memory is wrong or they decided not to support that. > Whether the domain is local to a JVM or made up of distributed part > accessible over TCP/IP Actually we can work this out for ourselves by seeing if there is a Node in the local JVM for that domain. The current sca-client-rmi supports doing this now. > In the remote case what IP endpoints information about the domain can > be exchanged with > In the remote case what protocol can be used to exchange this information > > Are there other snippets of info we are trying to configure? For > example, I'm sure we'll want to consider authority information at some > point. > >From the SCA perspective its just the the domain name (isn't it?), from the remote connectivity perspective looking at even just the config options available in the existing things we've tried (tribes, hazelcast, dht, zookeeper, ehcahce etc) shows a vast array of options we could expose. I think we can generalize the common ones so 90% of the time a simple uri format can be used (which is what the current tuscany uri format is trying to do, [1]), for the remaining cases i think we'll need to support pointing directly at a config file specific for the distribution technology being used) > And the more emotive (?) question of whether this information should > be presented directly in the domainURI or separated between the URI > and some external configuration of defaulting algorithm. > Supporting both approaches provides all the flexibility we need and seems like it should make everyone happy. > Sound right? > Yep [1] https://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/modules/endpoint-hazelcast/src/main/java/org/apache/tuscany/sca/endpoint/hazelcast/ConfigURI.java
