Re: Turbine, Fulcrum, and Avalon

[Leo Simons]

Jason van Zyl wrote:

On Tue, 2003-01-28 at 11:02, Leo Simons wrote:

Dan Diephouse wrote:

1. The component lookup mechanisms. Plexus includes a mechanism to have multiple comonents under the same role by extending Avalon's ServiceManager instead of just:

<snip/>

I can go into a multiple-week discussion with you about that. Seperation of Concerns, Inversion of Control, you know, the "religious avalon terms" :D

It certainly doesn't have to be a religious war, but I would certainly
take the opportunity to counter any of your arguments.

for some reason, it seems it is not possible to reach a broadly acceptable conclusion on things like this, yet most people have pretty strong ideas. Which is what I ment.

I didn't just rig
just anything into Plexus with thought, and strictly for convenience.

I didn't mean to imply otherwise. Did I? If so, apologies.

3. It is not mutually exclusive with other containers. That is, a component developed for ECM can work in plexus and vice versa.

reuse support is a tricky thing. If you do so much as

import org.zenplex.plexus.<whereisit>.ServiceBroker;

you're already on really thin ice. Once you get to

service( ServiceManager sm )
{ m_broker = (ServiceBroker)sm; }

you start losing compatibility real fast. Not that it won't work, but the effort to make it work will increase rapidly.

Not much a different situation that you have within Avalon where
components won't run in other containers.

yep. It's kinda annoying though, and important to minimize incompatibilities. The more common ground, the easier life is for the end user.

I think that will always
happen.

another difference of opinion :D

In fact Plexus specific components will have a somewhat
different lifecyle, for things that I believe are flawed with the
current lifecycle.

I'd be very much interested in hearing your reasoning on the various choices you made. Perhaps you can find time somewhere to get involved into the how-to-mod-the-lifecycle-debate :D

cheers,

- Leo



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