Re: Notice of scheduled work

On Sun, Jul 13, 2003 at 09:37:25PM -0400, Jason van Zyl wrote:
> I'm taking it out of the core of Plexus. Avalon can still be an
> API if that is desired. There's nothing special about the
> interfaces and they are deficient.

Cool.

> No Avalon components run in all containers anyway.

Huh; that shows my naivete.

I was under the assumption that if you stuck to the Avalon framework
API, and away from the container-specific classes/interfaces, you just
had to deal with different metadata/assembly information from container
to container. I thought the single component API and
hopefully-some-day-one-container-but-until-then-multiple-containers was
the whole point of Avalon.

That's disappointing.

I was going to ask if you even wanted other people outside of your
core group using Plexus yet (e.g. me), for perfectly valid reasons
(evolving API, don't want to provide support, etc.), more for the
motivation of I don't want to start implementing a system on Plexus
if it'll disappear.

But after looking over the Avalon site, it doesn't look like much has
changed in the last few months, and they seem to be in the same place
they were before. So perhaps Plexus is just a safe a gamble as
ECM/Fortress/Merlin.

Dunno, we'll see, I guess. Any sort of thing I attempt within a
component-based architecture is anywhere from a 1 to 9 months off, so
I'll continue lurking and dropping the occasional email in response to
your latest efforts, if you don't mind.

Thanks,
Stephen