On Jan 30, 2008 12:24 AM, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
> Simon Laws wrote: > [snip] > > The model in my sandbox [2], which is very simlar to the XML that the > > current contribution repository uses, now holds node and contribution > name > > information [3]. These could be two separate models to decouple the > > management of contributions from the process of associating them > together. > > I like the decoupling part: > > - A workspace containing contributions (basically just a contribution > URI -> URL association). I've started to add that Workspace interface to > the contribution package. > > - A description of the network containing nodes, we don't need a new > model for that, as we already have implementation-node and can use > something like: > > <composite name="bobsNetWork"> > > <component name="bobsNode1"> > <implementation.node ...> > </component> > > <component name="bobsNode2"> > <implementation.node ...> > </component> > > </composite> > > -- > Jean-Sebastien > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >From what you are saying a short term shopping list of functions seems to be emerging. Contribution uploader/manager(via browser) Contribution addition/management from command line (adding as Luciano has started this and useful for testing) Workspace to register added contributions contributions Parser to turn workspace contributions into a model that can be inspected (doesn't need the machinery of a runtime) Validator for validating contributions in a workspace Domain/Node model reader/writer (implementation.node) Function for assigning composites to nodes Function for processing assigned composites in the context of the domain (reference resolution, autowire) (again can be more lightweight than a runtime but does needs access to binding specific processing) Deployer for writing out contributions for nodes What else is there? Simon
