On Sun, 4 Nov 2001 22:52, Edison Too wrote: > Ok. After spending 1 day looking in Avalon/Phoenix and turbine, I have to > say that I can't go with Avalon this time round. Next time maybe.. :)
Turbine and Avalon/Phoenix serve largely different purposes. Turbine was primarily a web development platform though with turbine3 they are breaking it up better (still got excessive inter-dependencies). I am actually using part of it (Torque the OR-Mapping tool) in a swing application and it works great ;) Avalon/Phoenix is a host environment for applications assembled from services. It enforces the inversion of control principle in it's design and hopefully each application is relatively isolated from each other app. > One last question just to confirm I understand Avalon/Phoenix right: When > deploying multiple SAR on Phoenix, even if they use the same Block in their > assembly, each of them gets their own copy of the block. Is this correct? correct. -- Cheers, Pete ---------------------------------------------------------- Which is worse: Ignorance or Apathy? Who knows? Who cares? ---------------------------------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
