[
https://issues.apache.org/jira/browse/IMAP-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Norman Maurer updated IMAP-328:
-------------------------------
Fix Version/s: 0.3
Let us fix this for 0.3
> Better handle concurrent FETCH and EXPUNGE
> ------------------------------------------
>
> Key: IMAP-328
> URL: https://issues.apache.org/jira/browse/IMAP-328
> Project: JAMES Imap
> Issue Type: Improvement
> Affects Versions: 0.2.1
> Reporter: Norman Maurer
> Assignee: Norman Maurer
> Fix For: 0.3
>
>
> At the moment it MAY be possible for clients which do "slow" FETCHES to fail
> during stream the message content back to the client of another client (or
> session) EXPUNGE the same message at the same time. From a talk at ##imap
> (freenode irc) other IMAP Server implementations handle this kind of stuff
> more sensible (like dovecot and cyrus).
> There are a few options to handle this kind of stuff:
> 1) Lock the mailbox during FETCH and block EXPUNGE until its done
> 2) Only do a "pseudo" expunge and add it to some "commitlog" which will get
> executed when the FETCH is done. To be 100 % sure its necessary to store it
> permanet but I think in most cases a in memory representation MAY be enough
> I think 2) is the way to go
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
