Details
-
New Feature
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
0.4
-
None
-
None
Description
Context: IMAP4rev1 (RFC3501 requires that every message is identified by a stable 32-bit Unique Identifier (UID) assigned in incremental sequence. This is now achieved in James IMAP subproject (http://james.apache.org/imap) with a UidProvider interface implemented in memory. This implementation does not allow distributed working of the solution.
Task: A DistributedUidProvider must be designed. The design can rely on a distributed memory cache such as hazelcast , or any other solution (hadoop, hbase, cassandra,...), and implemented.
Mentor: eric at apache dot org
Complexity: medium
Attachments
Issue Links
- is depended upon by
-
JAMES-1387 [gsoc2012] Prepare James for running in a clustered setup - distributed James
- Closed