james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benoit Tellier (Jira)" <server-...@james.apache.org>
Subject [jira] [Created] (JAMES-3575) End to end reactive chain for Email update and JMAP RFC-8621
Date Sat, 01 May 2021 16:03:00 GMT
Benoit Tellier created JAMES-3575:

             Summary: End to end reactive chain for Email update and JMAP RFC-8621
                 Key: JAMES-3575
                 URL: https://issues.apache.org/jira/browse/JAMES-3575
             Project: James Server
          Issue Type: Improvement
          Components: JMAP, mailbox
            Reporter: Benoit Tellier
            Assignee: Antoine Duprat
             Fix For: 3.7.0

Giving a quick look around the code, I could figure out we can easily make the following JMAP-RFC-8621
calls fully reactive:

 - Email/set update (we not using range optimizations)
 - Email/set destroy

The JMAP RFC-8621 code is well organised, switching it to fully reactive is a no brainer.
Regarding the mailbox implementation they are already mostly reactive and the adjustments
needed feels minimal.

The JMAP draft code is not clean enough to benefit easily from this work.

By having a better thread management we empower better thread allocation, which results in
better tail latencies...

This message was sent by Atlassian Jira

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

View raw message