<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Event Streams on Nalar</title>
    <link>https://nalar.dev/tags/event-streams/</link>
    <description>Recent content in Event Streams on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 17 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/event-streams/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Linux inotify Events Are a Lossy Change Stream</title>
      <link>https://nalar.dev/linux-inotify-events-are-a-lossy-change-stream/</link>
      <pubDate>Thu, 17 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/linux-inotify-events-are-a-lossy-change-stream/</guid>
      <description>&lt;p&gt;An inotify file descriptor exposes filesystem activity as an ordered queue of event records, but that queue is not an authoritative history of namespace state. Identical unread events may be coalesced, queue capacity is bounded, and an overflow explicitly means events have been lost. A process that treats the stream as a complete transaction log can therefore preserve a state that no longer matches the filesystem.&lt;/p&gt;&#xA;&lt;p&gt;The interface is better modeled as change notification with recovery obligations. Events can make a cache current incrementally while the stream remains intact; some conditions invalidate that incremental history and require reconciliation against filesystem state.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
