Leo Simons wrote:
> gulp!
>
> Just got current versions of all CVS stuff. I'm lost!
> AAAAAH!
>
> -- just kiddin' --
>
> a few observations:
>
> - we have a DB
> - we have an FTP server
> - we have an event driven server architecture in the works
> - we have something called overlord and I can't really figure
> out what it does
> - we no longer like Poolables for some reason?
We don't like the interface Poolable. We like pooling.
> - we no longer like ComponentManager/Selector??
We no longer like the interface Component, as it does nothing but
bind us to Avalon. We want to enable using the framework with
components that cannot implement the Component interface for
whatever reason (i.e. CORBA components, etc.). Simply altering
ComponentManager/Selector is A Bad Thing (TM).
> - phoenix is working pretty well, the thing it really needs now
> being better management options
>
> ------
> I've been reading the archives on the ServiceManager discussion,
> but am quite failing to follow it all. What is the problem, what
> is the solution, do we agree on that yet and what will be the
> migration path?
The issue is that mere marker interfaces limit avalon too much.
The ServiceManager as is in CVS now is the stop gap solution
until we reach Avalon 5.0.
> I read up on SEDA, and really like it. Berin, you encountered
> problems with implementing it?
No, I just encountered problems getting time to implement it.
It's not easy...
> good to be back :-)
Good to have you back ;P
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
