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 "Matthieu Baechler (Jira)" <se...@james.apache.org> on 2020/04/28 08:25:00 UTC

[jira] [Updated] (JAMES-3153) Upgrade reactor to make use of retryWhen and RetrySpec

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

Matthieu Baechler updated JAMES-3153:
-------------------------------------
    Description: 
Latest reactor version include some new features regarding retry backoff (see https://github.com/reactor/reactor-core/pull/1979 )

As we were limited by the previous API, we did copy some code from reactor to workaround the limitations.

Now that they implement a RetrySpec, we should be able to get rid of this code duplication and rely on their well-tested feature.

h2. Definition of done:

* All reactive code should still work as before
* The code should use RetryWhen with RetrySpec instead of previous solutions


  was:
Latest reactor version include some new features regarding retry backoff (see https://github.com/reactor/reactor-core/pull/1979 )

As we were limited by the previous API, we did copy some code from reactor to workaround the limitations.

Now that they implement a RetrySpec, we should be able to get rid of this code duplication and rely on their well-tested feature.


> Upgrade reactor to make use of retryWhen and RetrySpec
> ------------------------------------------------------
>
>                 Key: JAMES-3153
>                 URL: https://issues.apache.org/jira/browse/JAMES-3153
>             Project: James Server
>          Issue Type: Improvement
>            Reporter: Matthieu Baechler
>            Priority: Major
>
> Latest reactor version include some new features regarding retry backoff (see https://github.com/reactor/reactor-core/pull/1979 )
> As we were limited by the previous API, we did copy some code from reactor to workaround the limitations.
> Now that they implement a RetrySpec, we should be able to get rid of this code duplication and rely on their well-tested feature.
> h2. Definition of done:
> * All reactive code should still work as before
> * The code should use RetryWhen with RetrySpec instead of previous solutions



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