<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Registering WebSocket connections with NiFi in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Registering-WebSocket-connections-with-NiFi/m-p/123665#M51287</link>
    <description>&lt;P&gt;&lt;A href="https://community.hortonworks.com/articles/73833/an-example-websocket-application-in-apache-nifi-11.html" target="_blank"&gt;https://community.hortonworks.com/articles/73833/an-example-websocket-application-in-apache-nifi-11.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;if they are connected to the websocket you can send them information from the flow.&lt;/P&gt;&lt;P&gt;You could also package that information into KAFKA or JMS and send them to a queue and a backend will pull from the queue and send the WebSocket messages.   That is probably more common to connect to the front end web.&lt;/P&gt;</description>
    <pubDate>Wed, 11 Jan 2017 09:04:24 GMT</pubDate>
    <dc:creator>TimothySpann</dc:creator>
    <dc:date>2017-01-11T09:04:24Z</dc:date>
    <item>
      <title>Registering WebSocket connections with NiFi</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Registering-WebSocket-connections-with-NiFi/m-p/123663#M51285</link>
      <description>&lt;P&gt;I’m working with NiFi WebSocket
processors, and I’d like to update connected clients as data makes its way
through the flow.  Is there a way to
register WS connections in such a way where once data makes its way to a PutWebSocket processor, I can push to all registered clients automatically?&lt;/P&gt;&lt;P&gt;Is this outside the scope of what NiFi may have been intended for?&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 11 Jan 2017 08:25:30 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Registering-WebSocket-connections-with-NiFi/m-p/123663#M51285</guid>
      <dc:creator>orendain</dc:creator>
      <dc:date>2017-01-11T08:25:30Z</dc:date>
    </item>
    <item>
      <title>Re: Registering WebSocket connections with NiFi</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Registering-WebSocket-connections-with-NiFi/m-p/123664#M51286</link>
      <description>&lt;P&gt;Hi Edgar,&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;I have tested a flow explained in this Gist to pull messages from Kafka then send it back to multiple connected clients.&lt;/P&gt;&lt;P&gt;&lt;A href="https://gist.github.com/ijokarumawak/60b9ab2038ef906731ebf4c0eee97176" target="_blank"&gt;https://gist.github.com/ijokarumawak/60b9ab2038ef906731ebf4c0eee97176&lt;/A&gt;&lt;/P&gt;&lt;P&gt;The flow does work, but it keeps flow files floating around in the loop and basically too difficult to setup.&lt;/P&gt;&lt;P&gt;The list of connected session ids are kept in WebSocket server controller service, so, theoretically it's possible to loop through those sessions in controller service without passing a specific session id from PutWebSocket processor. Maybe we can improve PutWebSocket processor so that it can send messages to every connected client.&lt;/P&gt;&lt;P&gt;I will create a JIRA for this improvement, in the meanwhile, please use the workaround like the above example flow.&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 11 Jan 2017 09:02:36 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Registering-WebSocket-connections-with-NiFi/m-p/123664#M51286</guid>
      <dc:creator>kkawamura</dc:creator>
      <dc:date>2017-01-11T09:02:36Z</dc:date>
    </item>
    <item>
      <title>Re: Registering WebSocket connections with NiFi</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Registering-WebSocket-connections-with-NiFi/m-p/123665#M51287</link>
      <description>&lt;P&gt;&lt;A href="https://community.hortonworks.com/articles/73833/an-example-websocket-application-in-apache-nifi-11.html" target="_blank"&gt;https://community.hortonworks.com/articles/73833/an-example-websocket-application-in-apache-nifi-11.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;if they are connected to the websocket you can send them information from the flow.&lt;/P&gt;&lt;P&gt;You could also package that information into KAFKA or JMS and send them to a queue and a backend will pull from the queue and send the WebSocket messages.   That is probably more common to connect to the front end web.&lt;/P&gt;</description>
      <pubDate>Wed, 11 Jan 2017 09:04:24 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Registering-WebSocket-connections-with-NiFi/m-p/123665#M51287</guid>
      <dc:creator>TimothySpann</dc:creator>
      <dc:date>2017-01-11T09:04:24Z</dc:date>
    </item>
    <item>
      <title>Re: Registering WebSocket connections with NiFi</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Registering-WebSocket-connections-with-NiFi/m-p/123666#M51288</link>
      <description>&lt;P&gt;Ah, gotcha.  Will use that workaround - thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 11 Jan 2017 09:07:37 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Registering-WebSocket-connections-with-NiFi/m-p/123666#M51288</guid>
      <dc:creator>orendain</dc:creator>
      <dc:date>2017-01-11T09:07:37Z</dc:date>
    </item>
    <item>
      <title>Re: Registering WebSocket connections with NiFi</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Registering-WebSocket-connections-with-NiFi/m-p/123667#M51289</link>
      <description>&lt;P&gt;A JIRA is created&lt;/P&gt;&lt;P&gt;&lt;A href="https://issues.apache.org/jira/browse/NIFI-3318"&gt;https://issues.apache.org/jira/browse/NIFI-3318&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Jan 2017 09:17:52 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Registering-WebSocket-connections-with-NiFi/m-p/123667#M51289</guid>
      <dc:creator>kkawamura</dc:creator>
      <dc:date>2017-01-11T09:17:52Z</dc:date>
    </item>
  </channel>
</rss>

