On Sun, Feb 14, 2010 at 11:49 PM, Simon Laws <[email protected]> wrote: > The thing about our slightly more dynamic approach to managing > endpoints across the domain that we have now is that we are not > precluding any particular approach to managing the domain in general. > The domain manager in 1.x is still as relevant now IMHO as a means of > managing the contributions in the domain and making them available to > the nodes that need them. The way that I look at it is that the set of > contributions can either be added to the manager and provided to the > nodes or added to the nodes and provided to the (notional) manager. > > It all comes down the where we manage the model of the contributions > and the relationship between them. > > Simon >
If anyone wants to look at a 2.x domain manager thats fine by me, but right now I think its more important to get the current distributed runtime working more completely and that means having contributions coming and going dynamically at runtime and having all the things they contribute - services, exports, wiring, policy, etc - just work as much as is possible. Right now I'm looking at the export function, i've not looked at the last two much yet, i posted about wires in the "Adding and removing wires dynamically" thread, if anyone wants to help with that or the policy piece that would be great. How we do all these in the runtime will likely change how a domain manager needs to work but once we've done these i do think some sort of manager GUI would be useful. ...ant
