GitHub user EronWright opened a pull request:

    https://github.com/apache/flink/pull/2766

    [FLINK-4898] Refactor HTTP handlers and Netty server/client

    - added support classes for REST and WebSocket-based protocols
    
    - generalized NettyClient/NettyServer: makes no assumptions about the
    channel pipeline, facilitates providing the initializer at connection
    time (to convey request-specific context such as a completion promise).
    
    - moved SSL handling to a standalone handler for composability
    
    - moved configuration constants related to the “partition request”
    protocol from NettyConfig to PartitionRequestNettyConfig

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/EronWright/flink feature-FLINK-4898

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/2766.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2766
    
----
commit 2926370baa43067a064990daff450ef63311d367
Author: wrighe3 <eron.wri...@emc.com>
Date:   2016-11-07T18:45:17Z

    [FLINK-4898] Refactor HTTP handlers and Netty server/client
    
    - added support classes for REST and WebSocket-based protocols
    
    - generalized NettyClient/NettyServer: makes no assumptions about the
    channel pipeline, facilitates providing the initializer at connection
    time (to convey request-specific context such as a completion promise).
    
    - moved SSL handling to a standalone handler for composability
    
    - moved configuration constants related to the “partition request”
    protocol from NettyConfig to PartitionRequestNettyConfig

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to