You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Ioan Eugen Stan (Updated) (JIRA)" <ji...@apache.org> on 2012/01/27 12:09:40 UTC
[jira] [Updated] (MAILBOX-103) Design and implement Distributed UID
generation
[ https://issues.apache.org/jira/browse/MAILBOX-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ioan Eugen Stan updated MAILBOX-103:
------------------------------------
Summary: Design and implement Distributed UID generation (was: [gsoc2011] Design and implement Distributed UID generation)
> Design and implement Distributed UID generation
> -----------------------------------------------
>
> Key: MAILBOX-103
> URL: https://issues.apache.org/jira/browse/MAILBOX-103
> Project: James Mailbox
> Issue Type: New Feature
> Components: hbase
> Affects Versions: 0.4
> Reporter: Eric Charles
> Assignee: Ioan Eugen Stan
> Fix For: 0.4
>
>
> 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
--
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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org