avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Berin Loritsch <blorit...@apache.org>
Subject Re: [proposal] AMTAGS (avalon meta tags)
Date Thu, 10 Apr 2003 12:40:04 GMT
Berin Loritsch wrote:
> Leo Simons wrote:
>> Berin Loritsch wrote:
>>> I would like to add (either in the
>>> x-avalon namespace or the avalon namespace):
>>> @avalon.role
>>>       Marks an interface as one that is designed to ALWAYS be exported.
>>>       I find it useful for 90% of all cases, and @avalon.service as
>>>       necessary for the remainder.
>> Bad idea. I may want to implement a work interface you wrote, but not 
>> export it. Implementors need the ability to "override" this kind of 
>> thing. It is okay to mark an interface as designed as a "work 
>> interface" in avalon scope, but making all classes which implement it 
>> export it "automatically" is _not_ a good idea and I know of at least 
>> one phoenix-based app it would totally break.
>> I understand the usecase (less typing!), but it will just cause too 
>> many hassles with existing apps.
> Existing apps wouldn't use it.  GUIApp would use it because ALL screens
> are screens, and any component implementing Screen is exporting that.
> Also, keep in mind the distinction of what is meant by "exporting".
> For example, Phoenix has a concept of exporting which makes the
> component accessible.

... outside Phoenix (i.e. JMX)

Sorry, I got distracted writing the email.

"You know the world is going crazy when the best
rapper is a white guy, the best golfer is a black guy,
The Swiss hold the America's Cup, France is
accusing the US of arrogance, and Germany doesn't want
to go to war. And the 3 most powerful men in America
are named 'Bush', 'Dick', and 'Colon' (sic)".

-----Chris Rock

To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org

View raw message