On Sun, 1 Sep 2002 02:36, Nicola Ken Barozzi wrote: > > <provides> > > <role> > > <key>conn-manager</key> > > <interface>org.apache.avalon.ConnManager</interface> > > </role> > > </provides> > > hmmm... component provides roles or services?
Traditionally it is Roles (ie interface+metadata) as we are now using the term. However Phoenix used the terminology "service" > Role=interface+metadata... yep. > <provides> > <service role="" interface=""/> > This is a cool service > </service> > <provides> so what does role="" mean in this context? Maybe give a fully fledged example so it is easier to understand. > > This means that; > > * The term "interface" would be reserved for designating the java > > interface. > > Hmmm... why "Java"? We can remain more generic. Okay - physical interface. That may mean IDL, C++ pure interface or whatever :) > > * Phoenix would adopt Fortress terminology wrt to Roles. ie a Role > > encompases an interface + metadata (if any). > > +1 for the concept, really neat. > > But I would not bind the meaning with "interface", which is Java > specific (ie language binding). > > A role is a Contract Moniker... yep! > or is it the key? Nope the key is "Role Key" or "Role Lookup Key" or whatever ;) > Isn't the distinction metadata-interface somewhat artificial conceptually? Not really. The programmer primarily deals in physical interfaces and it is what apears in our code. So we treat it very differently. -- Cheers, Peter Donald -------------------------------------------------- "An intellectual is someone who has been educated beyond their intelligence." -------------------------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
