Major 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...
Attachments
Issue Links
- links to
