Peter, that sounds like great news! I can't wait to see it.. I was going to implement for the various Fulcrum components the serviceable interface, should I wait? What changes do I need to use merlin as my container versus ECM?
Eric Pugh > -----Original Message----- > From: Peter Courcoux [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 24, 2003 11:27 PM > To: Avalon framework users > Subject: Re: pico container? > > > Glenn, > > Just for information, I have a Turbine Merlin Service, running > successfully on my local system. I have been corresponding > over the last > 10 days or so with Steve McConnell trying to understand a few issues > before taking it further. I hope that this will replace the ECM based > Avalon Component Service in Turbine in due course. > > My discussions with Steve have raised a few issues that may be of > interest to various users of Avalon and I will be posting my summary > shortly for discussion. > > Regards, > > Peter > > > On Wed, 2003-09-24 at 21:01, Glenn R. Golden wrote: > > 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] > -- > Peter Courcoux <[EMAIL PROTECTED]> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
