You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Nathan Gough (Jira)" <ji...@apache.org> on 2021/10/21 23:20:00 UTC

[jira] [Updated] (NIFI-9321) Refactor ListenTCPRecord to use Netty

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

Nathan Gough updated NIFI-9321:
-------------------------------
    Description: The {{ListenTCPRecord}} processor currently depends on {{SocketChannelDispatcher}}, which uses the custom {{SSLSocketChannel}} when enabled for TLS. The addition of Netty-based alternatives in {{nifi-event-transport}} removes the need for custom {{SSLEngine}} interaction and also streamlines the implementation of custom socket protocols.  (was: The {{ListenTCP}} processor currently depends on {{SocketChannelDispatcher}}, which uses the custom {{SSLSocketChannel}} when enabled for TLS. The addition of Netty-based alternatives in {{nifi-event-transport}} removes the need for custom {{SSLEngine}} interaction and also streamlines the implementation of custom socket protocols.)

> Refactor ListenTCPRecord to use Netty
> -------------------------------------
>
>                 Key: NIFI-9321
>                 URL: https://issues.apache.org/jira/browse/NIFI-9321
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: 1.15.0
>            Reporter: Nathan Gough
>            Assignee: Nathan Gough
>            Priority: Minor
>              Labels: TLS, security
>
> The {{ListenTCPRecord}} processor currently depends on {{SocketChannelDispatcher}}, which uses the custom {{SSLSocketChannel}} when enabled for TLS. The addition of Netty-based alternatives in {{nifi-event-transport}} removes the need for custom {{SSLEngine}} interaction and also streamlines the implementation of custom socket protocols.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)