Uploaded image for project: 'James Server'
  1. James Server
  2. JAMES-3575

End to end reactive chain for Email update and JMAP RFC-8621

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 3.7.0
    • JMAP, mailbox
    • None

    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

          Activity

            People

              aduprat Antoine Duprat
              btellier Benoit Tellier
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 50m
                  50m