You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Joseph Witt (JIRA)" <ji...@apache.org> on 2015/09/27 20:19:04 UTC
[jira] [Commented] (NIFI-1002) support for Listen WebSocket
processor
[ https://issues.apache.org/jira/browse/NIFI-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14909832#comment-14909832 ]
Joseph Witt commented on NIFI-1002:
-----------------------------------
Very much like the idea. We've definitely been asked about web socket support over the years. I think it makes a lot of sense for both of these listen/put to be processors. Would request that you consider shifting to maven instead of Gradle for build management so it will be consistent with the rest of NiFi. That will be important for merging/reviewing the PR.
Thanks
Joe
> support for Listen WebSocket processor
> ---------------------------------------
>
> Key: NIFI-1002
> URL: https://issues.apache.org/jira/browse/NIFI-1002
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 0.4.0
> Reporter: sumanth chinthagunta
> Priority: Minor
> Labels: newbie
>
> A WebSocket listen processor will be helpful for IoT data ingestion.
> I am playing with embedded Vert.X for WebSocket and also ability to put FlowFiles back to WebSocket client via Vert.X EventBus.
> https://github.com/xmlking/nifi-websocket
> I am new to NiFi. any advise can be helpful.
> PS: I feel forcing Interfaces for Controller Services is unnecessary as in many cases Controller Services are only used by a set of Processors and developers usually bundle them together.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)