Why Does Qlik Sense Use WebSocket?Article Number: 000030282 | Last Modified: 2018/06/12
- Client initiated data update, server does not push updates to client
- Interval based polling for updates, always a latency in data being updates on client side
- Data updates are hard to predict, making it hard to plan polling interval
- XML structured data, leading to big overhead during transfer
- Client or server can intiate data transfer, the WebSocket remains open during the entire web session
- The communciiotn is full-duplex, meaning that either side can use the full bandwidth
- Data is typically transferred in JSON instead of XML, leading to minimal over-head
- Communicaiton can carry any data, text or binary
Have a Question?
Search Qlik's Support Knowledge database or request assisted support for highly complex issues.Submit a case
Experiencing a serious issue, please contact us by phone. View phone numbers and hours by region.