Ok then answers in line but if you articulated your concerns instead of put them behind questions things might go faster ...
On Thu, Sep 11, 2008 at 5:19 PM, Raymond Feng <[EMAIL PROTECTED]> wrote: > My concerns are behind the questions you trimmed :-). Answers to these > questions will help me understand your approach. I relist the questions > below. > > 1) What's the result of the discovery? A list of SCA nodes (for example, > node.composite that describes the node configuration)? > A network of ActiveMQ brokers > > > 2) Do we have a "manager" that initiate the discovery and maintain the > membership dynamically? > No > > 3) Where are the SCA contributions from? Is this part of the discovery? > Something tells the node about them, right now in this initial code that would be the user at node startup > > 4) Which part is responsible to manage the SCA contributions and resolve > composites at the domain level? The input to a SCA node is a deployable > composite and a list of SCA contributions (contribution uri + location). > > What you've said is just the way the current org.apache.tuscany.sca.node APIs work, ideally they would be extended to support this approach better (which is what i was suggesting in the 2nd email in this thread) > 5) I cannot find samples/helloworld-distributed. Where is it? > https://svn.apache.org/repos/asf/tuscany/java/sca/samples/helloworld-distributed > > 6) Can you describe the steps in sequence for this approach? I would like > to > see how the players interact in this dynamic fashion and what information > is > produced from each interaction. > Could you try the sample and see if it helps you understand? ...ant
