> What are the objectives, if they are more than re-use? Can you identify > them?
stuff like: - clean code - common program flow in code - instant well-designed architecture - speed etc etc. I doesn't matter that much to me whether you reuse stuff I write at all. I care about well-designed software. Reuse is an added benefit. The benefits of using avalon are partially the same as those of reuse, RAD, etc. Partially, they are the same as those of Design Patterns. Basically, avalon is about (a common) java server software architecture (like all frameworks are about defining a common architecture) on the one hand, and about providing specific parts of that server architecture on the other hand (like all component libraries). What you ask thus is "what are the objects of software architecture design?" and "what are the benefits of component libraries?" The answers are all over the place; many apply to avalon. - Leo Simons -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
