[
https://issues.apache.org/jira/browse/JAMES-3078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
René Cordier closed JAMES-3078.
-------------------------------
Fix Version/s: 3.5.0
Resolution: Done
> Refactoring jmap-draft to be reactive with reactor-netty
> --------------------------------------------------------
>
> Key: JAMES-3078
> URL: https://issues.apache.org/jira/browse/JAMES-3078
> Project: James Server
> Issue Type: Sub-task
> Reporter: René Cordier
> Assignee: René Cordier
> Priority: Major
> Fix For: 3.5.0
>
>
> We need to make jmap-draft use a server based on reactor-netty, instead of
> jetty (james-server-jetty). For this, you need to:
> # create a new module jmap that will implement the server with its
> configuration, and will be used as the meta project redirecting to the right
> jmap version being requested (see #1639)
> # port the code of jmap-draft to use the new netty server instead of jetty.
> Features that are directly being leveraged by jetty are:
> ** user/mailbox provisioning
> ** authentication filters
> ** request routing
> In order to succeed this refactoring, you can:
> * Create a HTTP server:
> https://projectreactor.io/docs/netty/release/reference/index.html#http-server
> * Port request routing:
> https://projectreactor.io/docs/netty/release/reference/index.html#_routing_http
> and
> https://projectreactor.io/docs/netty/release/reference/index.html#_consuming_data_3
> * It seems there is no high level methods to manage filters, so you will need
> to manage it manually in each route
> _Reference material_:
> https://projectreactor.io/docs/netty/release/reference/index.html
> *DoD*: Successful port to reactor-netty with all the tests passing for
> jmap-draft
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
