> > I'm not interested in the technical parts (interceptors). But more how
> > Phoenix's relation to Avalon in general will evolve.
> Would you accept the consensus of this development community on that
> project or you would do an internal fork everytime you get a -1?
> I think *this* (more than any technical stuff) is what is important at
> this point.
Speaking for myself, I view Avalon as providing a container oriented
architecture of which Phoenix is a container implementation.
So long as the Avalon project provides us with a suitable container on which
we can host James, I think we're happy. I'd like to see code migration
issues minimized, although it shouldn't impact our end-users because we ship
as one unit.
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
