<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Locking on Luther Monson</title>
    <link>https://luth.io/tags/locking/</link>
    <description>Recent content in Locking on Luther Monson</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 13 Oct 2026 20:40:00 -0700</lastBuildDate>
    <atom:link href="https://luth.io/tags/locking/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A Lock Is Only as Good as Its Release</title>
      <link>https://luth.io/blog/2026/10/a-lock-is-only-as-good-as-its-release/</link>
      <pubDate>Tue, 13 Oct 2026 20:40:00 -0700</pubDate>
      <guid>https://luth.io/blog/2026/10/a-lock-is-only-as-good-as-its-release/</guid>
      <description>&lt;p&gt;Every &amp;ldquo;build a lock on Redis&amp;rdquo; tutorial spends its time on acquisition: &lt;code&gt;SET key value NX PX 30000&lt;/code&gt;, one winner, done. The&#xA;release gets one line, &lt;code&gt;DEL key&lt;/code&gt;. That line is where most of the lock bugs I&amp;rsquo;ve had in ePHPm lived. Over about three&#xA;months the same mistake showed up in three places. First the native session handler, then two of the Composer wrapper&#xA;packages, and finally the cluster. Each time it wore a slightly different costume.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
