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/05/01 16:23:00 UTC
[jira] [Updated] (JAMES-3575) End to end reactive chain for Email
update and JMAP RFC-8621
[ https://issues.apache.org/jira/browse/JAMES-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benoit Tellier updated JAMES-3575:
----------------------------------
Description:
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 - for keywords and mailboxIds (when not using range optimizations)
- Email/set destroy
The JMAP RFC-8621 code is well organized, 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...
was:
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...
> 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
> Priority: Major
> Fix For: 3.7.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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 - for keywords and mailboxIds (when not using range optimizations)
> - Email/set destroy
> The JMAP RFC-8621 code is well organized, 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
(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