I'm new to Avalon, and I really like it. I've got some experience with Turbine services from Jetspeed and we use the ideas of services in our project (chefproject.org). I'm looking for our next generation service methodology.

Then I ran across Pico Container, and read the stuff on their web site. I think I grok the essential difference between Avalon Framework and Pico Container - they like to have all the dependent components delivered to a component in the constructor, while in Avalon you ask for other components when you need them.

I'm not sure what to make of this difference. Pico is much simpler (?). But what am I loosing for that simplicity?

If anyone cares to comment on the Pico v.s. Avalon Framework question, I'd be happy to listen.

Thanks.

- Glenn

Glenn R. Golden  CHEF Architect
System Research Programmer III
School of Information + Media Union @ University of Michigan
[EMAIL PROTECTED]


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to