[
https://issues.apache.org/jira/browse/JAMES-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefano Bagnara resolved JAMES-491.
-----------------------------------
Resolution: Fixed
Fix Version/s: (was: Trunk)
Next Major
Marking this as fixed. The first step has been done.
IF someone think there is a need for the remaining steps to be implemented then
feel free to open a new ad-hoc issue.
> SpoolManager refactorings
> -------------------------
>
> Key: JAMES-491
> URL: https://issues.apache.org/jira/browse/JAMES-491
> Project: James
> Issue Type: Improvement
> Components: SpoolManager & Processors
> Affects Versions: 2.3.0
> Reporter: Stefano Bagnara
> Assigned To: Stefano Bagnara
> Fix For: Next Major
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
