<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>SignalR on Nalar</title>
    <link>https://nalar.dev/tags/signalr/</link>
    <description>Recent content in SignalR on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 19 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/signalr/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>FCM Is a Wake-Up Path, Not a Real-Time Transport</title>
      <link>https://nalar.dev/fcm-is-a-wake-up-path-not-a-real-time-transport/</link>
      <pubDate>Sat, 19 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/fcm-is-a-wake-up-path-not-a-real-time-transport/</guid>
      <description>&lt;h1 id=&#34;fcm-is-a-wake-up-path-not-a-real-time-transport&#34;&gt;FCM Is a Wake-Up Path, Not a Real-Time Transport&lt;/h1&gt;&#xA;&lt;p&gt;A mobile application can maintain a WebSocket while it is active and still need Firebase Cloud Messaging when the operating system suspends it. Those mechanisms solve different failure conditions.&lt;/p&gt;&#xA;&lt;p&gt;WebSocket, MQTT, and SignalR assume that a client can participate in a live communication session. FCM is useful precisely when that assumption no longer holds: the application may be backgrounded, its process may not be running, or its persistent connection may have disappeared.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
