The following is a brief description of my experiences with Avalon. I have come to appreciate smaller focused tools that do one thing really well. Veloctiy, Log4j, etc. If a smaller tool turns out to be unsatisfactory, it takes some work to replace it but that is just an inconvenience rather than a major setback. Committing to a framework on the other hand is a big decision which I have up until now been reluctant to do. Many of the web development frameworks seem too ambicious and intrusive for my comfort level. The more a development tool/framework attempts to do for me, the more dependant my code becomes. I don't want to feel like I have to conform to one development style. Avalon, being a general server development framework strikes a nice balance. It doesn't attempt to do 'web development' which is very good. Naturally this also makes it useful for not just website development but other types of server development projects.
I approached Avalon with the same caution as I have with other projects. I took bits and pieces as I felt comfortable. Avalon's flexability allowed me to do this. I didn't have to make any all-or-nothing decisions. Actually, I originally used Avalon without applying any Avalon code in my projects. I found it to be a rich source of good programming ideas and examples. I have been learning more about Avalon, feeling more confidant and I am now enthusiastically applying Framework and Excaliber in my projects. > There are quite a few people here who are new to Avalon or working on > their own Avalon dependant applications. Could as many people as > possible contribute a short list of reasons why they are using or like > Avalon's Framework, Excalibur or Phoenix. -- Kerry Todyruik <[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
