<?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 API Course</title>
    <link>https://apicourse.com/tags/websockets/</link>
    <description>Recent content in WebSockets on API Course</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 02 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://apicourse.com/tags/websockets/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Real-Time APIs: WebSockets, Server-Sent Events, and Long Polling</title>
      <link>https://apicourse.com/real-time-apis-websockets-server-sent-events-and-long-polling/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      <guid>https://apicourse.com/real-time-apis-websockets-server-sent-events-and-long-polling/</guid>
      <description>&lt;p&gt;Standard HTTP is a request-response protocol: the client sends a request, the server sends a response, the connection closes or is returned to a pool. This model is efficient for most API use cases. It is the wrong model when the server needs to push data to the client without waiting for a client request — live dashboards, chat applications, collaborative editing, real-time notifications, trading feeds. Three patterns exist to bridge this gap, each with a different complexity profile and a different set of constraints.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
