On Mon, 26 Nov 2001 10:41, Uli Mayring wrote: > But Avalon being a framework and Phoenix a platform, there might be a > user-level where IoC is optional. Interoperability is an important concept > today. Nobody will use this framework and platform, if it is not at some > level interoperable with legacy applications. So far things look good, but > isn't it a pain in the ass, when you cannot just implement something you > need because of IoC? :)
Avalon/Phoenix needs to maintain IOC in it's communication with Blocks - or else it would not have been possible to host multiple applications. There are things that apps can do to get around this and some wont effect other apps but some will. So in a lot of ways the reason for IOC is less good design but isolation of applications (luckily it also is good design ;-}). It won't be until JDK1.5 is out and the Isolate API comes into use where apps can throw caution to the wind and do whatever they want without messing up other apps. Phoenix will definetly be supporting this mode of operation ... wont encourage bad programming though ;) -- Cheers, Pete ------------------------------------------------------- "I would like to take you seriously but to do so would affront your intelligence" -William F. Buckley, JR ------------------------------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
