[JAMES-3535] Implement Identity/changes

• Type: Sub-task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.6.0
• Component/s: JMAP
• Assignee: Antoine Duprat
• Reporter: Benoit Tellier
• Created: 04/Apr/21 10:58
• Updated: 09/May/23 02:12

Description

https://jmap.io/spec-mail.html#identitychanges

This is a standard “/changes” method as described in [@!RFC8620], Section 5.2.

By having a per account, state indexed, time ordered changelog we would be able to answer that call. This is somehow similar to what had been done for mailbox/email. The API of this changelog can be defined in server/data/data-jmap and would need a memory and a Cassandra implementation.

Except that Identity/set could take care of updating the changelog without the need to rely on the eventBus (as it will not be modified by other protocols). Also note that identity being not delegated, delegation is not a concern.

Push support for identity can be achieved by having the Identity/set method pushing directly a StateChange on the JMAP eventBus.