On Fri, Jan 22, 2010 at 5:47 PM, Raymond Feng <[email protected]> wrote: > Hi, > > I came across a scenario where multiple Nodes are created from the same > NodeFactory. For example, in an OSGi framework, we have a singleton of > NodeFactory which internally maintains the ExtensionPointRegistry. Two Nodes > (A and B) with the same domain URI are created from the NodeFactory. These > two Nodes will share the same EndpointRegistry as they have the same > domainURI and domainRegistryURI. Node A publishes an endpoint to the > EndpointRegistry and it will be seen by Node B. In this case, we cannot tell > if the endpoint from A is local or remote to B. As a result, binding.sca > cannot decide if it should handle the invocation from B to A as a local or > remote one. > > I propose that we add domainURI and nodeURI to the RuntimeEndpoint model and > they will be propagated as part of the endpoint descriptions across Nodes > via the SCA domain endpoint registry. This way, we don't have to depend on > the registry's membership management to tell if an endpoint is from the same > or different node. > > If there is no objection, I'll make the changes. >
Is there any chance you could hold off on this till next week? I can't really clearly say why right now, i'm just getting back up running on another temporary machine this evening and hoping to spend the weekend recovering the weeks work after having two machines fail, and would like to try to get at least some basic distributed domain working properly by Monday. We've still not closed any of the threads about how the domain and/or registry URIs might work, and from the old Node API thread you can see I don't even think we need a Node URI so I'd like to understand better this suggestion and see if there's alternatives to that being used in the endpoint registry. ...ant
