[
https://issues.apache.org/jira/browse/IGNITE-15132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-15132:
-----------------------------------------
Description:
At the moment - RestModule prepares its own Netty infra for handling requests.
But it will be great to have one root Netty pools and etc. configs and just
separate handlers.
Also, maybe we should use the "one port for all operations" concept for REST
API too.
Perhaps, this link may be useful https://groups.google.com/g/netty/c/WT6ZxvvFR-E
was:
At the moment - RestModule prepares its own Netty infra for handling requests.
But it will be great to have one root Netty pools and etc. configs and just
separate handlers.
Also, maybe we should use the "one port for all operations" concept for REST
API too.
> REST API must reuse general netty infrastructure from network module
> --------------------------------------------------------------------
>
> Key: IGNITE-15132
> URL: https://issues.apache.org/jira/browse/IGNITE-15132
> Project: Ignite
> Issue Type: Task
> Reporter: Kirill Gusakov
> Priority: Major
> Labels: ignite-3, tech-debt
>
> At the moment - RestModule prepares its own Netty infra for handling
> requests. But it will be great to have one root Netty pools and etc. configs
> and just separate handlers.
> Also, maybe we should use the "one port for all operations" concept for REST
> API too.
>
> Perhaps, this link may be useful
> https://groups.google.com/g/netty/c/WT6ZxvvFR-E
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
