Stefano Bagnara wrote:
> Noel J. Bergman wrote:
>>>> Handlers should know nothing about Avalon. Let's please get
>>>> that code out of there, and stop putting more in.
> > Just the handlers. [I] just don't want to push that API any deeper.
> You know that Avalon currenlty flow through the veins of James, and not
> only in top level components.
It used to be kept out of MOST of the Matchers and Mailets. IIRC, at one point
it was only in RemoteDelivery, and then I added it (by necessity) to the quota
code. Likewise, Mark did evil :-) things with the CommandListServ
configuration code.
> Before you cast more vetoes I would like to know how you will handle
> Avalon removal in the core.
There really is very little of Avalon that we depend upon. What we do use
pervades the service code, and is unfortunately exposed because the Mailet API
is anemic.
> In the end we will have to decide how to manage our
> "managed components"
Yes. We'll need to be clear and clean about our containers and their
interfaces. We need a container for matchers/mailets, a container within the
protocol handler for those components, etc.
The Processor is the container for the Mailet API. The spooler is the
container for the processor.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
