> From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED]] > > Peter Donald wrote: > > On Sat, 23 Nov 2002 07:56, Stepanossov, Kirill wrote: > > > >>I apologies for interfering your discussion but wasn't > Phoenix a kind of > >>Proof-of-Concept behind Avalon and its ideas ? I conceived > Phoenix as a > >>project which helped to polish major conceptions and to > prove that they > >>were viable in production environment and exactly what was > needed for > >>server-side development. But at a certain point due to its > success Phoenix > >>started being seen as a major Avalon achievement and lost > its initial > >>meaning. Is this picture wrong ? > > > > > > It has it's origins in the original Avalon container but it > has been > > completely rewritten from the ground up about 5 times. Two > classes still > > remain from original iteration (one deprecated). It was > originally intended > > to be the "one" container for Avalon but when Cocoon forked > off it kept > > evolving. > > what are you talking about? Cocoon uses ECM which, the name > "extensible > component manager" suggests, was the simplest embeddable Avalon > component manager around when Cocoon needed one. Tell me: > where is the fork?
Umm, Actually that is "Excalibur Component Manager". However, Cocoon had it first, and then with the efforts of both me and Giacomo, we made it more generic and moved it to Excalibur. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
