[ http://issues.apache.org/jira/browse/JAMES-491?page=all ]
Stefano Bagnara updated JAMES-491:
----------------------------------
Fix Version/s: Trunk
(was: Next Major)
The split into 3 layers have been done, but the refactoring to implement
different schedulers has not been implemented. Moving to trunk.
> SpoolManager refactorings
> -------------------------
>
> Key: JAMES-491
> URL: http://issues.apache.org/jira/browse/JAMES-491
> Project: James
> Issue Type: Improvement
> Components: SpoolManager & Processors
> Affects Versions: 2.3.0rc3
> Reporter: Stefano Bagnara
> Assigned To: Stefano Bagnara
> Fix For: Trunk
>
>
> JamesSPoolManager and LinearProcessor should be refactored in 3 layers:
> 1) the spoolmanager: create threads and worker, accept mails and pass them to
> the "mail processor"
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
