On Tue, Apr 21, 2009 at 4:37 PM, ant elder <[email protected]> wrote: > Ok yes i agree with all that, it is the purpose of the SCAClient. And that > reinforces the point that the impl should be separate from the Node. I know > the current code has NodeImpl implementing SCAClient but that was just a > easy way to demonstrate SCAClient working, so i'll create a new SCAClient > impl for this. > > ...ant
...snip Back in the good/bad (delete as appropriate) old days when we first started with the node and domain idea the node implemented both node and domain interfaces and, using the domain interface on the node, you could retrieve a reference to any service available in the domain by exploiting binding.sca under the covers regardless of whether the local node was actually running that component. This worked well but it felt awkward in it's attachment to the local node. So a long way of saying +1 to creating a new and separate SCAClient. Two thoughts... - a first step could just be to interact with a local node and note any restrictions - to move beyond this requires some new interfaces on the domain manager as the old ones that made this work were removed (but we could do with some for the more dynamic scenarios of late binding and being able to start nodes in arbitrary orders so that's a good discussion to have) Simon
