[jira] [Commented] (NIFI-3318) Send message from PutWebSocket to all connected clients

["Edgar Orendain (JIRA)" <ji...@apache.org>]

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

Edgar Orendain commented on NIFI-3318:
--------------------------------------

[~jeremy.dyer] I'm happy to help test the patch if it's in a shareable state.  NiFi WS is something I'm demo'ing in a reference app, though I may have to temporarily drop it unless I can find a cleaner workaround than what I have atm.

> Send message from PutWebSocket to all connected clients
> -------------------------------------------------------
>
>                 Key: NIFI-3318
>                 URL: https://issues.apache.org/jira/browse/NIFI-3318
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Koji Kawamura
>            Assignee: Jeremy Dyer
>
> Currently, PutWebSocket processor needs an incoming flow file having a WebSocket session id attribute to tell the NiFi WebSocket server which connected client to send a message to.
> A flow explained in this [Gist|https://gist.github.com/ijokarumawak/60b9ab2038ef906731ebf4c0eee97176] to pull messages from Kafka then send it back to multiple connected clients works, but it keeps flow files floating around in the loop, and basically too difficult to setup. Also, it imposes unnecessary latency because it needs to poll a cache to see if there's new message.
> The list of connected session ids are kept in WebSocket server controller service, so it's possible to loop through those sessions in controller service without passing a specific session id from PutWebSocket processor.
> PutWebSocket processor can be improved so that it can send messages to every connected client.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)