Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129817
Precedence: list
MIME-Version: 1.0
References: <CAMW7n8B9XHzF5ND21-hNYtw26EnE+0b+W0Nv=wb_ayMmu4CbKw@mail.gmail.com>
 <CAMW7n8C1m08+pKKYBGkMnNZmGmu-_kkxS-r_SCuRupBY+RHe5A@mail.gmail.com>
 <CANCsWvfXWDjdmKFFQvV0Ger6yNVSfOhQqnbyTr7bEQHSjmXyLg@mail.gmail.com> <79CDB2CC-E397-436E-B5A2-10DA1E451A97@rwec.co.uk>
In-Reply-To: <79CDB2CC-E397-436E-B5A2-10DA1E451A97@rwec.co.uk>
Date: Wed, 21 Jan 2026 20:09:45 +0200
Message-ID: <CAMW7n8CvVD4zNGELeYV3MWP2z0bRgF6jA0WWnafCkNE8-Ka4BQ@mail.gmail.com>
Subject: Re: [PHP-DEV] Re: [RFC] True Async RFC 1.7
Cc: php internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
From: edmond.ht@gmail.com (Edmond Dantes)

How the TrueAsync RFC evolved over time:

The first version proposed a fairly low-level API for controlling the
Scheduler, philosophically very close to AMPHP. It quickly became
clear that this approach had many drawbacks, including issues with
consistent PHP behavior.

The code was completely rewritten. Core changes became more
significant. In the second version, the PHP execution flow was changed
so that any code could be asynchronous.
The second RFC version introduced structured concurrency, close to
modern equivalents.
At the same time, the garbage collector code was rewritten several
times. One version went through code review, after which a simplified
variant appeared. Today, Async GC exists in a lightweight form.
The implementation code was modified and optimized according to
approaches used in Swoole.
The next RFC version received fixes and improvements to the
description. The RFC was split into several parts and significantly
reduced in size.
Around this point, the first vote and major discussions took place.
Their result was the creation of a working group. Another important
outcome was the integration of Fibers as coroutine generators, which
removed the problems of previous RFCs.
Various experiments were conducted, extended memory models were
tested, and Globals isolation was explored. WordPress and Laravel were
run as stateful applications under FrankenPHP + TrueAsync.
A small MVP was written for a multithreaded PHP memory manager capable
of correctly working with PHP objects across different threads. The
possibilities of sharing and transferring memory between PHP threads
were investigated.

Compared to document 1.6, document 1.7 contains one new section:
Fiber. Everything else remains without significant changes.

Best regards, Ed