<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Concurrency Control on Nalar</title>
    <link>https://nalar.dev/tags/concurrency-control/</link>
    <description>Recent content in Concurrency Control on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 16 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/concurrency-control/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>HTTP If-Match Turns Representation State Into a Write Precondition</title>
      <link>https://nalar.dev/http-if-match-turns-representation-state-into-a-write-precondition/</link>
      <pubDate>Wed, 16 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/http-if-match-turns-representation-state-into-a-write-precondition/</guid>
      <description>&lt;p&gt;An HTTP origin can refuse a &lt;code&gt;PUT&lt;/code&gt; or &lt;code&gt;DELETE&lt;/code&gt; before applying it when the request carries &lt;code&gt;If-Match&lt;/code&gt; and the selected representation no longer has an accepted entity tag. The condition converts a representation validator into a write precondition: a client can say that a mutation is valid only against state matching a version it previously observed.&lt;/p&gt;&#xA;&lt;p&gt;This mechanism addresses a specific concurrency boundary. It can prevent one client from silently replacing resource state after another client has changed the selected representation. It does not turn HTTP into a transaction protocol, lock the resource between requests, or guarantee that an entity tag represents every piece of application state involved in a mutation.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
