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 "Benoit Tellier (Jira)" <se...@james.apache.org> on 2021/04/04 11:00:02 UTC
[jira] [Updated] (JAMES-3535) Implement Identity/changes
[ https://issues.apache.org/jira/browse/JAMES-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benoit Tellier updated JAMES-3535:
----------------------------------
Description:
https://jmap.io/spec-mail.html#identitychanges
{code:java}
This is a standard “/changes” method as described in [@!RFC8620], Section 5.2.
{code}
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.
was:
https://jmap.io/spec-mail.html#identitychanges
{code:java}
This is a standard “/changes” method as described in [@!RFC8620], Section 5.2.
{code}
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.
> Implement Identity/changes
> --------------------------
>
> Key: JAMES-3535
> URL: https://issues.apache.org/jira/browse/JAMES-3535
> Project: James Server
> Issue Type: Sub-task
> Components: JMAP
> Affects Versions: 3.6.0
> Reporter: Benoit Tellier
> Assignee: Antoine Duprat
> Priority: Major
>
> https://jmap.io/spec-mail.html#identitychanges
> {code:java}
> This is a standard “/changes” method as described in [@!RFC8620], Section 5.2.
> {code}
> 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.
--
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