An article on The Server Side (http://www.theserverside.com/home/thread.jsp?thread_id=22371) started me thinking again about HiveMind today. The major issues mentioned there are the same as mentioned by Howard below:
> > I've looked to see how we could graft HiveMind into Avalon and vice-versa, > > but they are really quite different beasts. The type-1 vs. type-2/type-3 > > split is intrinsic and difficult to reconcile. HiveMind's concept of a > > module doesn't map so easily into the Avalon space, and HiveMind's > > free-for-all approach doesn't jive with Avalon's dogmatic security model > > (including its explicit application construction descriptor). Are these really incompatible concepts? Isn't Merlin, for example, trying to do more with auto-assembly? Doesn't our model allow us to push services to be used rather than having to pull them from a service manager? I really don't see why this is an either-or issue. Likewise, free-for-all vs security can be viewed as a policy. I suggest that people give some thought to how TO collaborate with HiveMind and Avalon. I think that the combination of people and technologies could be great. --- Noel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]