[
https://issues.apache.org/jira/browse/JAMES-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3575.
---------------------------------
Resolution: Fixed
Most of JMAP draft and JMAP RFC-8621 are now reactive.
Remains (blocking style) for both draft & JMAP-8621:
- attachment download/upload
- attachment validation upon Email/create
- range updates (flags + move)
> 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: 50m
> 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-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
