On Thu, Jan 15, 2009 at 1:44 PM, Simon Laws <[email protected]>wrote:
> > > On Thu, Jan 15, 2009 at 9:08 AM, ant elder <[email protected]> wrote: > >> >> >> On Mon, Jan 12, 2009 at 10:15 AM, Simon Laws >> <[email protected]>wrote: >> >> <snip> >> >> >>> The Tuscany domain is static in that all contributions must be present >>> before you start nodes. I'd like to see us move toward a more dynamic >>> solution but we aren't there yet. >>> >> >> More dynamic operation is a common requirement that keeps on coming up, >> how about we make it a design point that 2.0 will support a more dynamic >> mode of operation? >> >> ...ant >> >> >> > I think I would go along with that but we should talk about what we mean by > dynamic, for example here are a couple of things that could be dynamic > > - nodes can be started/restarted while the contributions in the domain > remain static > - contributions can be added/removed from the running system > > Personally I'm interested in the first one to start with which I believe > can be achieved by sorting out our endpoint/late binding support [1]. This > addresses some dynamic infrastructure scenarios I'm interested in; > > - I want to start a node and have it added to the domain automatically (we > can exploit the addNode interface I hope and, with endpoint support, allow > nodes to come up independently) > - I want to stop and restart a node (this one is probably OK now) > - I want to relocate a node (relies on endpoint support) > > I haven't thought any more about the second one. There are more > complications here IMO. > > Simon > > [1] http://www.mail-archive.com/dev%40tuscany.apache.org/msg04476.html > > > Great. Both of those options you mention sound useful to me, I'm more interested in the second of those right now for one as thats what we need for the Tuscany integration with Geronimo its also the type of thing has been requested several times by users. Anyway, i'd be happy to help with both. ...ant
