<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Websockets on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/websockets/</link>
    <description>Recent content in Websockets on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 11 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/websockets/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted WebSocket Proxies: Whistle vs Proxyee vs WebSocketProxy</title>
      <link>https://www.pistack.xyz/posts/2026-05-11-self-hosted-websocket-proxies-whistle-proxyee-koding-guide/</link>
      <pubDate>Mon, 11 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-11-self-hosted-websocket-proxies-whistle-proxyee-koding-guide/</guid>
      <description>&lt;p&gt;WebSocket technology enables persistent, bidirectional communication between clients and servers — essential for real-time chat, live dashboards, collaborative editing, gaming, and IoT telemetry. As WebSocket adoption grows, the need for dedicated WebSocket proxying infrastructure becomes critical.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
