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 2020/06/18 04:31:00 UTC

[jira] [Closed] (JAMES-3149) Extend reactive coverage in JMAP draft

     [ https://issues.apache.org/jira/browse/JAMES-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benoit Tellier closed JAMES-3149.
---------------------------------
    Resolution: Fixed

This effort is done.

> Extend reactive coverage in JMAP draft
> --------------------------------------
>
>                 Key: JAMES-3149
>                 URL: https://issues.apache.org/jira/browse/JAMES-3149
>             Project: James Server
>          Issue Type: Improvement
>          Components: JMAP
>    Affects Versions: 3.5.0
>            Reporter: Benoit Tellier
>            Assignee: Antoine Duprat
>            Priority: Major
>              Labels: perf
>             Fix For: 3.6.0
>
>
> 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.



--
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