[IMAP-141] Refactor the store api to provide a generic / thread safe reserveNextUid() implementation

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Fix Version/s: 0.1
• Component/s: Mailbox
• Assignee: Unassigned
• Reporter: Norman Maurer
• Created: 09/May/10 15:45
• Updated: 14/May/10 11:03
• Resolved: 14/May/10 11:03

Description

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.