RE: SMTPHandler

Stephen,

> are you familar with what I need to do to address
> the Avalon changes so that GUMP can build us properly?

> The changes that were applied to Cornerstone several months
> ago (retraction of Component, and the replacement of Composable with
> Serviceable) simply create too many problems

No comment regarding the notion of deprecation, and breaking interfaces
within major release boundaries.  In any event ...

>   a) we (Avalon) rollback Cornerstone to implement ComponentManager
>      + addition of Component to the inhertance graph of
>      related components

Is anyone other than James complaining about the interface change(s)?

>   b) upgrading James to use ServiceManager

> I would suggest proceeding with option (b)

> the transition from Composable to Serviceable is not too difficult
> is just a matter of some specific replacements and a some
> validatition - the more relavant question is when?

Well, that's why I asked.  What exactly do we need to do?  We may not do it
for James v2, but I'd like James v3 (HEAD) to be able to float against
Avalon.

	--- Noel