<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Need to keepalive a QWebSocket?]]></title><description><![CDATA[<p dir="auto">I've used TCP Sockets in my apps before, and I've had to send regular noop/dummy data across the connection to keep it open (since a TCP socket is just a dumb pipe) to prevent the host or firewalls etc from closing the connection if idle.</p>
<p dir="auto">What about websockets?  I'm not familiar with the details of their implementation, but do they do their own keepalive?  Or do I need to send an occasional command (or something) across the websocket?</p>
]]></description><link>https://forum.qt.io/topic/155158/need-to-keepalive-a-qwebsocket</link><generator>RSS for Node</generator><lastBuildDate>Sun, 14 Jun 2026 12:21:49 GMT</lastBuildDate><atom:link href="https://forum.qt.io/topic/155158.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 07 Mar 2024 20:29:13 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Need to keepalive a QWebSocket? on Thu, 07 Mar 2024 20:38:40 GMT]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">I think it's the <a href="https://doc.qt.io/qt-6/qwebsocket.html#ping" target="_blank" rel="noopener noreferrer nofollow ugc">ping</a> method you are looking for.</p>
]]></description><link>https://forum.qt.io/post/792525</link><guid isPermaLink="true">https://forum.qt.io/post/792525</guid><dc:creator><![CDATA[SGaist]]></dc:creator><pubDate>Thu, 07 Mar 2024 20:38:40 GMT</pubDate></item></channel></rss>