On Thursday 11 March 2004 08:25, Roy Henderson wrote: > I don't ( yet ) understand exactly how the container and the > application fit together and which does what piece of the overall process.
Well, the container enables runtime pluggable modules, and wiring of these without compiler/linker support. In your case, it means that you can potentially write an additional/replacement component for James, change the "assembly.xml" and have Phoenix use your component "as well" or "instead of some other". In VB lingo, it is like all the DLL's where pulled in and configured according to a textfile, and not hardcoded in the VB code, and of course all written in the same language. > One thing which is worth listening to though. As a potential user of an > Avalon-contained application, I am a bit concerned to hear that there is > some debate on the function and direction of the product ... perhaps I > should select Exim or Postfix instead of James ... James has a life beyond that of Avalon, but even if James is currently running on top of Phoenix, there are at least one person (Stephen McConnell) running James on top of Merlin, and the code changes required for that is in the James CVS. In a way, James works as a giant testcase for the ongoing development of Merlin. Niclas -- +---------//-------------------+ | http://www.bali.ac | | http://niclas.hedhman.org | +------//----------------------+ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
