>So, chip in, even if you think that your "story" is nothing to tell. If you
>are new to Avalon, please indicate what you think is attractive and what >you >have problems with. It doesn't have to follow Aaron's 'questionaire' to the >dot, it is just a guidance... I am actually a die-hard VB programmer who is wrestling with learning Java so I don't know how relevant my comments will be. However, as invited: My only real exposure to Avalon so far has been to use Phoenix as the container for James which I am evaluating as a possible mail server for my ISP venture. I don't ( yet ) understand exactly how the container and the application fit together and which does what piece of the overall process. Perhaps one day I will complete Java-101 and find a use for a container. If it can provide configurable, common, reusable services which I can incorporate into my applications ... then ... I'm interested. I don't understand quite why there are multiple ( 4 ? ) container variants - although I believe that they are actually just 2 generations of 2 variants. But, when I develop that first application, which container do I select, and more importantly, why? 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 ... I'm not particularly looking for replies to my comments / questions because they're not meant to generate tangential discussions distracting from the original thread ... just some user comment Regards, Roy ---------------------------------------------------------------- [This message has been routed via James V2.1.3 on REBEX-MERCURY] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
