[
https://issues.apache.org/jira/browse/IMAP-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Norman Maurer resolved IMAP-141.
--------------------------------
Resolution: Won't Fix
We dedicited to use implementation specific locking for this
> Refactor the store api to provide a generic / thread safe reserveNextUid()
> implementation
> -----------------------------------------------------------------------------------------
>
> Key: IMAP-141
> URL: https://issues.apache.org/jira/browse/IMAP-141
> Project: JAMES Imap
> Issue Type: Bug
> Components: Mailbox
> Reporter: Norman Maurer
> Fix For: 0.1
>
>
> At the moment the reserveNextUid() method in StoreMailbox is abstract and
> need to get implemented by every Implementation. I think we should try to
> provide a "generic" implementation which could be used by every
> implementation. This method needs to be "thread-safe" and need to make sure
> that the uid consuming is a atomic operation so that no "ghost reads" can
> happen.
--
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]
