[JAMES-3149] Extend reactive coverage in JMAP draft

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.5.0
• Fix Version/s: 3.6.0
• Component/s: JMAP
• Labels: perf
• Assignee: Antoine Duprat
• Reporter: Benoit Tellier
• Created: 14/Apr/20 06:48
• Updated: 18/Jun/20 04:30
• Resolved: 18/Jun/20 04:30

Description

JMAP relies on reactor-netty for it's HTTP layer. The Cassandra layers, ElasticSearch layers relies on reactor too.

Some calls to `block` in the middle prevent us from having an optimal thread usage.

We should enforce where we can the reactive chain to be unaltered in order to optimize resource usage.

This had been contributed for GetVacationResponse, SetVacationResponse, GetFilter, SetFilters.

We can easily contribute this for GetMailboxes and GetMessageList.