> > Never going to use an interface again for this. If you remember back
> > about 1 1/2 years ago we separated out interface and implementations for
> > the meta classes. It sucked hugely.
>
> I don't know if it sucked or it spit :-) , but what is the need of
> having an interface versus implementation?
> Will there be many implementations, one for each container? Why is it
> needed?
It seems there may indeed be multiple implementations. FA, Stephen has
already extended metadata (think it is called "profile" or something).
The main reason I chose to use interfaces in the setup is that
interfaces (at least at avalon) imply contracts rather than
implementations, and I feel what we should be discussing is contracts
instead of implementation details.
> Since this is just a "structure" (no "real" methods), it seems that
> using interfaces is not needed.
yup.
> Yes, why are they here?
> What would they be used for?
> I don't understand.
simple enough: to pass to the component. You can see this as a
formalization of phoenix its ApplicationEntry (if that still exists....)
> I think we should standardize on some common stuff to describe
> components, ie
> - version
> - role
> - description
>
> Where is doesn't make sense, a default version or description is used.
yup. There is some stuff in containerkit already to do this. Basically,
there is
- role
- service description
[version, classname, attributes]
- attributes
> > -1
> > Selection criterion are context sensitive and can be relegated to a
> > particular container implementation.
>
> Selection cretarion are "context sensitive"? You mean that selection
> is done depending on what you have to select?
>
> I don't think so, assembly semantics *has* to be the same if we want
> things to work between containers.
Nah, as soon as you start discussing "possible alternatives" the
selection between different alternatives can be container specific (I
*think* that's what he ment, anyway).
- Leo
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
