Paul Hammant wrote:

Avalon Phoenix: establishes the server, rules, and
contracts for hosting server applications.

Ahem... One of our containers, establishing its own rules and contracts for hosting server (and
non server) applications. Rules, that is, beyond the ubiquitious Avalon-Framework interfaces.


This is a very delicate point.

Phoenix is big, really big. IMV it's at the same level of Avalon, and should be a project in its own right.

I dunno, what do the Phoenix guys think that should be done, given that we should unite?

+1

Paul:

Could you clarify for me your +1.
Are you saying you support the seperation of Phoenix into a project PMC, or are you saying that Phoneix should be part of the united Avalon?

Cheers, Steve.

-ph


__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com

--
To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>




--

Stephen J. McConnell

OSM SARL
digital products for a global economy
mailto:mcconnell@;osm.net
http://www.osm.net




--
To unsubscribe, e-mail:   <mailto:avalon-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>

Reply via email to