On Fri, 21 Mar 2003 01:21, Berin Loritsch wrote:
> The only thing holding up consensus is you.

Same with the marker interfaces we have or will be deprecating. Same with the 
compatability stuff that is in framework.

> So what would it take to
> change your mind?
>
> I am asking for three standard names:
>
> @avalon.component (in phoenix already)
> @avalon.service   (in phoenix already)

this is used differently in phoenix from the way you proposed. I suggested 
that @avalon.role may be a better marker tag.

> @avalon.lifestyle (proposed)
>
> I don't recall us comming to consensus on avalon.component and
> avalon.service and yet you chose to use the avalon namespace.

Lazy consensus. If you have a problem with them then state it.

> So I want to add one more standard name, what's the problem from
> your viewpoint?

I think that the avalon namespace should be restricted to defining resources 
that the component requires or provides. lifestyle is not one of those 
things. 

Even if it was I don't think it is mature enough to be supported for all time. 
Besides not being able to represent all of the potential lifestyles such as 
"pooled during times X and y, transient other times" or "passivate under 
condition X"

Hell - I don't even think the lifecycle concept is something we should be 
marking up. I have described quite a few times in the past of a method via 
which lifestyle could be broken down into atomic bits of metadata 

ie

lifecycle=single-thread       := ( sharable=true,  multiclient=true  )
lifecycle=factory/transient   := ( sharable=false, multiclient=false )
lifecycle=poolable            := ( sharable=false, multiclient=true )

etc.

Then the container can read the metadata about the component and determine how 
it will be handled. ie A component that is "poolable" can also be treated as 
"transient/factory" if the container wants without effecting the client code 
or component code. It effectively becomes a configuration decision and 
tunable by the container. Even better it is future compatible.

Anyways if you want to try an develope a set of those then we can try that 
(but then again I think they will need time to mature anyways).

-- 
Cheers,

Peter Donald
"The ability to quote is a serviceable substitute for wit." -- Maugham 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to