[
https://issues.apache.org/jira/browse/NIFI-3318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15936982#comment-15936982
]
Jeremy Dyer commented on NIFI-3318:
-----------------------------------
I have ran into a situation where I need this badly. I have a patch that I plan
to test out over the next few days and will submit once I have tested it out
more throughly
> 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)
