cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sylvain Wallez <sylv...@apache.org>
Subject Re: [RT] Some notes about the "Real Blocks" issue
Date Thu, 14 Oct 2004 12:19:21 GMT
Vadim Gritsenko wrote:

<snip/>

> Personally, I'd favor Avalon support for chosen container. As Ralph 
> noted, and he is not alone, people like Avalon, and we should support 
> it for years to come.


Well, people will like DI containers once they start using them :-)

> So why to run two containers - one too much - if Avalon support can be 
> implemented in new container of choice. More memory, management, and 
> confusion overhead. And people also would ask why two containers if 
> old is still there and is used 99% of time (and that's where you 
> answer on my question above - what's so cool about new container - helps).


I share your opinion. It would be better to provide an Avalon 
compatibility layer with the new container that having the old ECM still 
inside.

Sylvain

-- 
Sylvain Wallez                                  Anyware Technologies
http://www.apache.org/~sylvain           http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }


Mime
View raw message