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 "Antoine Duprat (JIRA)" <se...@james.apache.org> on 2016/10/10 10:35:20 UTC

[jira] [Resolved] (JAMES-1825) message uid deserves its own type

     [ https://issues.apache.org/jira/browse/JAMES-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Antoine Duprat resolved JAMES-1825.
-----------------------------------
    Resolution: Fixed

merged

> message uid deserves its own type
> ---------------------------------
>
>                 Key: JAMES-1825
>                 URL: https://issues.apache.org/jira/browse/JAMES-1825
>             Project: James Server
>          Issue Type: Improvement
>            Reporter: Matthieu Baechler
>
> As usual, the fact that imap rfc describes message uid as a long influenced the way James was build.
> We use long everywhere and often messed up between message sequence and message uid in the code base.
> We could very well use a MessageUid type everywhere to make sure what we are handling.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org