james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Norman Maurer (JIRA)" <server-...@james.apache.org>
Subject [jira] Updated: (JAMES-491) SpoolManager refactorings
Date Fri, 07 Jul 2006 06:51:38 GMT
     [ http://issues.apache.org/jira/browse/JAMES-491?page=all ]

Norman Maurer updated JAMES-491:

    Fix Version: 3.0
                     (was: 2.4.0)

> SpoolManager refactorings
> -------------------------
>          Key: JAMES-491
>          URL: http://issues.apache.org/jira/browse/JAMES-491
>      Project: James
>         Type: Improvement

>   Components: SpoolManager & Processors
>     Versions: 2.3.0
>     Reporter: Stefano Bagnara
>     Assignee: Stefano Bagnara
>      Fix For: 3.0

> JamesSPoolManager and LinearProcessor should be refactored in 3 layers:
> 1) the spoolmanager: create threads and worker, accept mails and pass them to the "mail
> 2) JamesProcessor: manage a list of processors and pass the mail to the processor given
its current state
> 3) LInearProcessor: remain almost unchanged, but handle its own configuration.
> The 3 objects could be transformed in toplevel components in order to remove the ContainerUtil
usage and have a better codebase to run in different containers.
> The final goal would be to have a modular spoolmanager: we could then introduce an OutgoingSpoolManager
that simply implement the current "scheduling" and people could wire together spoolmanagers
and mail processors as they prefer.
> It also makes more sense to have the RemoteDelivery in a top level component instead
of using Mailet instantiated threads.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message