Hi Raymond Just noticed this post from last week...
Interesting thought. At the moment all the definitions in the domain are collected together into a system contribution which (in the 1.x way of thinking) would be passed to each node along with the contributions it needs to run with. Effectively each node has a copy of the whole domain's policy configuration. I think what you are suggesting is extending the endpoint registry more toward a domain registry so that you can ask about available policies and intents as well as configured endpoints. I.e. instead of each node asking for its complete configuration when it starts, it's able to look up information in the domain registry as and when required. I quite like this idea as it feels more likely to be able to support future dynamic scenarios than the one-shot approach we have in 1.x. However the flipside is increased network traffic and there will be a greater number of infrastrure service interfaces. I'd like to understand how various scenarios would work with a scheme like this. Not sure that that wider conversation belongs on this thread though it's really a summary of what was discussed on [1]. I'll post something as a followup to that. Regards Simon [1] http://www.mail-archive.com/[email protected]/msg09220.html
