On Tuesday 09 March 2004 15:43, Stephen McConnell wrote: > > Component Type Specification > > Component Instance Identification Specification > > New territory for avalon but this is in the realm of managable stuff.
This is also already in place to some degree. We have the issue regarding Merlin semantics of "/somecontainer/somecomponent", but that refers to a "semi-instance", as it depends on what LifeStyle that component is declared with. There are heaps of other 'holes' here. > > Component Dependency Specification > > Atructural is in place but I figure you thinking about the availability > contract - no? Partly. Currently there is no strict contract, just an implicit contract defined in the container implementations. The beginning has started in form of "@avalon.dependency" but I am sure, once one start digging into "optional" and what should actually happen when dependencies can not be fulfilled, we are in a whole new ballgame. Details are not relevant right now. > > Component Packaging Specification > Mre braincells need to die before this is closed. Without it, it is no point dealing with the "Great Vision", and I will continue the "Great Vision" elsewhere. But I do agree, there is room for plenty of contention here. > > Component Requirements Extension Specification > Can you explain this one in more detail? Well, it must be possible to create new contracts in the future, which are either brand new, evolution of existing or replacements of existing specifications. That means that the container that is created today need to know how to behave when new contracts (which it doesn't understand) are going to be treated, "fail" or "ignore" and how the components can signal this contracts and behaviours. So, this field is about "A specification on how to create new specifications." But this is just the beginning of "missing pieces". Niclas -- +---------//-------------------+ | http://www.bali.ac | | http://niclas.hedhman.org | +------//----------------------+ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
