On Thu, 20 Mar 2003 07:57, Berin Loritsch wrote:
It's a name for crying out loud, what's to mature?
And Poolable is just a marker interface for crying out loud, whats to mature?
Its code.
All we are doing is establishing the name, and some values that could be used.
Is that too much to ask?
no - but why do you need to do it in avalon namespace. When there is consensus then standardize on it. (And I do not consider consensus to be simple majority votes).
The only thing holding up consensus is you. 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) @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.
So I want to add one more standard name, what's the problem from your viewpoint?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
