<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Php Internals on Luther Monson</title>
    <link>https://luth.io/tags/php-internals/</link>
    <description>Recent content in Php Internals on Luther Monson</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 30 Jul 2026 20:18:00 -0700</lastBuildDate>
    <atom:link href="https://luth.io/tags/php-internals/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Building a Custom SAPI - How PHP Actually Talks to the Outside World</title>
      <link>https://luth.io/blog/2026/07/building-a-custom-php-sapi/</link>
      <pubDate>Thu, 30 Jul 2026 20:18:00 -0700</pubDate>
      <guid>https://luth.io/blog/2026/07/building-a-custom-php-sapi/</guid>
      <description>&lt;p&gt;If you&amp;rsquo;ve only ever run PHP behind nginx, you&amp;rsquo;ve probably never had to think about how &lt;code&gt;echo&lt;/code&gt; reaches a socket. When&#xA;you embed PHP like &lt;a href=&#34;https://github.com/ephpm/ephpm&#34;&gt;ePHPm&lt;/a&gt; does, it&amp;rsquo;s the first thing you have to answer. The answer&#xA;is a SAPI. There is very little written about implementing one. Most of what I know came from reading &lt;code&gt;sapi/cli&lt;/code&gt;,&#xA;&lt;code&gt;sapi/cgi&lt;/code&gt; and &lt;code&gt;sapi/embed&lt;/code&gt; in php-src. Then I found out which parts I&amp;rsquo;d misread. This is the write-up I wanted back&#xA;in March.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
