>Gerhard Froehlich wrote:
>>
>> Hi Stefano,
>> can you give a clear separation to Phoenix and Avalon 5?
>
>Sorry, I can't really parse the question.
>
>What do you mean?
Oh sorry. I was a little bit in a hurry at the weekend.
I follow two main architectural discussions in the moment:
(1) The Avalon 5 Design on the Avalon dev. list
(2) Cocoon Block Design here
Both approaches want the same:
"Provide a component oriented framework, where you can easy plugin
Components
on runtime".
I know there are lot of Cocoon and Avalon related details in this two
concepts,
but this is IMHO the common denominator.
Peter Donald and Berin Loritsch wrote interesting RTs last days and I see
lot of parallels to your COB proposal:
<http://marc.theaimsgroup.com/?l=avalon-dev&m=102513578616579&w=2>
<http://marc.theaimsgroup.com/?l=avalon-dev&m=102449360809559&w=2>
Therefor I'm little bit concerned that we have double functionality in the
future,
especialy when Avalon 5 is coming. I'm concerned that we have a framework
in a
framework, which IMAO doesn't make things easier than now:
My worst scenario:
As a Cocoon 3.0 Developer I must develop my Cocoon components as Avalon 5
components
and promote them to the internal Avalon 5 ComponentContainer with the
special
Avalon procedure.
In a second step I have to promote the Cocoon components to the Cocoon
Kernel or whatever
with the special Cocoon procedure.
You see what I mean?
But I'm sure that you already made your thoughts about this topic. I just
want
to hear your opinion and maybe you can sweep off my concerns in one
sentence :-).
What I want is a short comparsion of this two architecures dicussions in
the moment.
Greets
Gerhard
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
