<?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>topic How to determine if there is an available WebSocket connection? in Connectivity &amp; Data Prep</title>
    <link>https://community.qlik.com/t5/Connectivity-Data-Prep/How-to-determine-if-there-is-an-available-WebSocket-connection/m-p/121252#M661</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are imbedding Qlik visualizations in our company website and we are trying to solve an issue with WebSockets.&amp;nbsp;&amp;nbsp; Initially, we were opening several Qlik Applications to build the page and, in IE especially, we hit the limitation on the number of available WebSockets.&amp;nbsp; We have reduced the number of WebSockets needed, but if the user opens the site on multiple tabs, we can still run out of available WebSockets.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are trying to do one of two thing to help this.&amp;nbsp;&amp;nbsp; Either, determine the number of available WebSockets before we attempt to open a new Qlik Application and, if none are available, inform the user so they can close some of the open tabs.&amp;nbsp;&amp;nbsp; If we can't proactively determine if there is a WebSocket available, then the alternative would be to trap an error that tells us that there wasn't an available WebSocket and inform the user of the failure.&amp;nbsp;&amp;nbsp; Right now, all we get is a blank page with no visualizations loaded and no indication of why.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With WebSocket connections being so critical for Qlik, I am wondering if anyone else has dealt with this issue and developed a way to determine WebSocket availability, either before or after the event.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Del- &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 24 Aug 2018 19:56:01 GMT</pubDate>
    <dc:creator>dellamb19</dc:creator>
    <dc:date>2018-08-24T19:56:01Z</dc:date>
    <item>
      <title>How to determine if there is an available WebSocket connection?</title>
      <link>https://community.qlik.com/t5/Connectivity-Data-Prep/How-to-determine-if-there-is-an-available-WebSocket-connection/m-p/121252#M661</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are imbedding Qlik visualizations in our company website and we are trying to solve an issue with WebSockets.&amp;nbsp;&amp;nbsp; Initially, we were opening several Qlik Applications to build the page and, in IE especially, we hit the limitation on the number of available WebSockets.&amp;nbsp; We have reduced the number of WebSockets needed, but if the user opens the site on multiple tabs, we can still run out of available WebSockets.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are trying to do one of two thing to help this.&amp;nbsp;&amp;nbsp; Either, determine the number of available WebSockets before we attempt to open a new Qlik Application and, if none are available, inform the user so they can close some of the open tabs.&amp;nbsp;&amp;nbsp; If we can't proactively determine if there is a WebSocket available, then the alternative would be to trap an error that tells us that there wasn't an available WebSocket and inform the user of the failure.&amp;nbsp;&amp;nbsp; Right now, all we get is a blank page with no visualizations loaded and no indication of why.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With WebSocket connections being so critical for Qlik, I am wondering if anyone else has dealt with this issue and developed a way to determine WebSocket availability, either before or after the event.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Del- &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Aug 2018 19:56:01 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Connectivity-Data-Prep/How-to-determine-if-there-is-an-available-WebSocket-connection/m-p/121252#M661</guid>
      <dc:creator>dellamb19</dc:creator>
      <dc:date>2018-08-24T19:56:01Z</dc:date>
    </item>
  </channel>
</rss>

