james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrzej Rusin (JIRA)" <server-...@james.apache.org>
Subject [jira] [Commented] (IMAP-370) Consider supporting the upcoming MOVE extension
Date Fri, 07 Dec 2012 11:45:20 GMT

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

Andrzej Rusin commented on IMAP-370:
------------------------------------

Eric, 

Thanks for comments.

Lock: the difference is that COPY does not alter the source folder content, while MOVE does.
That's my concern. But maybe there is some way to safely lock both folders?
OTOH, for the implementations that MOVE makes any sense, it will be very quick and atomic
(that's the whole point of MOVE). So - not having lock is less unsafe than it seems.
For implementations that can't do MOVE quickly it does not make much sense.

I probably do not know maildir and jpa MMs to implement MOVE correctly. Someone needs to help.

Let's discuss the legacy MOVE after we have the basic MOVE in place.

What would be the next steps?

Thanks,
Andrzej
                
> 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-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