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 "René Cordier (Jira)" <se...@james.apache.org> on 2020/12/28 07:47:00 UTC
[jira] [Closed] (JAMES-3469) Implement MemoryEmailChangeRepository
[ https://issues.apache.org/jira/browse/JAMES-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
René Cordier closed JAMES-3469.
-------------------------------
Fix Version/s: 3.6.0
Resolution: Done
> Implement MemoryEmailChangeRepository
> -------------------------------------
>
> Key: JAMES-3469
> URL: https://issues.apache.org/jira/browse/JAMES-3469
> Project: James Server
> Issue Type: Sub-task
> Reporter: Lan Khuat
> Priority: Major
> Fix For: 3.6.0
>
>
> From the spec: [https://jmap.io/spec-core.html#changes]
> {code:java}
> When the state of the set of Foo records in an account changes on the server (whether due to creation, updates, or deletion), the state property of the Foo/get response will change.
> {code}
> We need to store all the changes made to mailbox objects in a table name EmailChangeRepository. First we will implement a memory version of it.
> h1. How
> 1. Define EmailChange model with these fields:
> * accountId
> * state
> * created
> * updated
> * destroyed
> * date
> 2. Implement APIs to interact with MemoryEmailChangeRepository (save, getFromState)
> h1. DoD
> Write unit tests to show that MemoryEmailChangeRepository is functioning properly.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org