flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-4898) Refactor HTTP handlers and Netty server/client
Date Mon, 21 Nov 2016 15:59:59 GMT

    [ https://issues.apache.org/jira/browse/FLINK-4898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15683935#comment-15683935
] 

ASF GitHub Bot commented on FLINK-4898:
---------------------------------------

Github user mxm commented on the issue:

    https://github.com/apache/flink/pull/2766
  
    Thanks for the PR, @EronWright. I think @uce is most familiar with the network layer.
Just wondering from a first quick look, if the code removes duplicate implementation of network
components by providing a common base, why are there so little lines removed? We still have
to port the existing code I assume?


> Refactor HTTP handlers and Netty server/client
> ----------------------------------------------
>
>                 Key: FLINK-4898
>                 URL: https://issues.apache.org/jira/browse/FLINK-4898
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Cluster Management
>            Reporter: Eron Wright 
>            Assignee: Eron Wright 
>            Priority: Minor
>
> The dispatcher requires an HTTP stack, ideally with a minimum of dependencies and able
to interoperate with Netty 4.0.28 (on which Flink currently depends).  The `runtime-web` module
has some home-grown HTTP handlers already, and the `runtime` module has some low-level Netty
code worth reusing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message