james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Brewin (JIRA)" <server-...@james.apache.org>
Subject [jira] Updated: (JAMES-509) Cleanup/Refactor FetchMail code
Date Sun, 01 Apr 2007 19:52:32 GMT

     [ https://issues.apache.org/jira/browse/JAMES-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Steve Brewin updated JAMES-509:

    Priority: Minor  (was: Major)

Swtched priority from major to minor.

Stefano, if this is now off your roadmap please close the issue.

> Cleanup/Refactor FetchMail code
> -------------------------------
>                 Key: JAMES-509
>                 URL: https://issues.apache.org/jira/browse/JAMES-509
>             Project: James
>          Issue Type: Improvement
>          Components: FetchMail
>    Affects Versions: Next Major
>            Reporter: Stefano Bagnara
>         Assigned To: Stefano Bagnara
>            Priority: Minor
>             Fix For: Trunk
>         Attachments: fetchmail-refactoring1, fetchmail-refactoring2, james-imap2-proposal-extended-2.zip
> Current FetchMail code is really hard to read and manage.
> I loose too much time looking around its code to understand how things works.
> So I put my hands in, and applied a few refactoring.
> I already removed 2200 lines of code (50Kbytes of code) while keeping the same functionality
(only refactorings).
> Of course refactorings like this are not always an easy change: I also remove the StoreProcessor/FolderProcessor/MessageProcessor
granular creation by refactoring them to top level reentrant objects that take things to process
as arguments to their "process" method.
> MessageProcessor is still a mess, but I think this is more selfdocumenting than before.
> I can clean up things much more and update documentation and so on, but I would like
to know if this kind of update is welcome or not, before loosing too much time.
> Stefano

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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message