On Thursday 13 November 2003 05:45, Noel J. Bergman wrote: > > > 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 agree. Merlin could reasonably easily be extended to support "Constructor construction/configuration", and currently Merlin doesn't support the strict security (right?), like phoenix does (did, RIP!) Niclas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
