james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Charles (JIRA)" <server-...@james.apache.org>
Subject [jira] [Commented] (IMAP-370) Consider supporting the upcoming MOVE extension
Date Wed, 06 Feb 2013 06:43:12 GMT

    [ https://issues.apache.org/jira/browse/IMAP-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13572220#comment-13572220
] 

Eric Charles commented on IMAP-370:
-----------------------------------

Hi Andrzej,
I finally had to remove the MoveProcessor from the chain as it was breaking the connection
when a copy command was issued by the client.
This is due to the AbstractChainedProcessor.isAcceptable method which relies on Class.isInstance
to see if the processor is valid for the command.
In this particular case, as Move extends Copy, the condition is fullfilled and the move is
assigned to the copy.
The ideal would be to use composition instead of extension.
I am happy to discuss any valid proposal (change the isAcceptable logic...) although I would
prefer the composition approach keeping the isAcceptable as it is now.

Thx, Eric
                
> Consider supporting the upcoming MOVE extension
> -----------------------------------------------
>
>                 Key: IMAP-370
>                 URL: https://issues.apache.org/jira/browse/IMAP-370
>             Project: James Imap
>          Issue Type: Improvement
>          Components: Protocol
>            Reporter: Andrzej Rusin
>         Attachments: IMAP-370-capability-v1.patch, IMAP-370-v1.patch
>
>
> As we see at http://datatracker.ietf.org/doc/draft-ietf-imapmove-command/ballot/ IETF
is about to finally accept the IMAP MOVE extension.
> This extension enables great performance optimization possibilities for the more advanced
Mailstore backends, eg the ones that use a underlying relational or non-relational database:

> One of the most common usage scenarios in IMAP is moving messages across folders, and
with the MOVE extention it can be finally accomplished without a COPY/DELETE cycle on certain
Mailbox backends.
> Therefore, in my belief, it would be very nice to have that extension implemented in
James.
> Some of the bundled Mailstore implementations already are based on SQL/noSQL datasources,
and can directly benefit from it.
> Some of the independent Mailstore implementations (including mine) can benefit from it
too.
> Some of IMAP clients (including Thunderbird as of 3.something) already support that extension
or the X-MOVE or X-AOL-MOVE one.
> So James has a great opportunity to be the leader of standards adoption on the server
side.
> What do you think? Please comment.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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


Mime
View raw message