Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126409
Precedence: bulk
MIME-Version: 1.0
References: <CAMW7n8CcNuttyxhtDeG1apHFVjU_9sKAhf0RG890b82Q1AnJpw@mail.gmail.com>
 <CAEKnhAFX-RnmRwgP_OoMs_fV2J_NWrfbEvUMDqMwgp_Td4JrOQ@mail.gmail.com>
In-Reply-To: <CAEKnhAFX-RnmRwgP_OoMs_fV2J_NWrfbEvUMDqMwgp_Td4JrOQ@mail.gmail.com>
Date: Fri, 14 Feb 2025 14:28:07 +0100
Message-ID: <CAEKnhAFg5aTQwWr9=2HNmAUkeOKdQfBiFhoioH91HicoG6ANzw@mail.gmail.com>
Subject: Re: [PHP-DEV] PHP True Async
To: Edmond Dantes <edmond.ht@gmail.com>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary="000000000000cd0c81062e1a258a"
From: bukka@php.net (Jakub Zelenka)

--000000000000cd0c81062e1a258a
Content-Type: text/plain; charset="UTF-8"

>
>
>> A brief overview of what this RFC will cover:
>>
>>    1. *True* asynchronous support for PHP core functions without
>>    additional "tricks."
>>    2. *Scheduler* and *Reactor* components, providing a C-API for PHP
>>    extensions to enable non-blocking I/O in plugins or core code.
>>    3. *User-Land API* that mirrors the C-API for PHP developers.
>>    4. Basic primitives for concurrent programming, such as *Channel* and
>>    *Iterator*.
>>    5. *Built-in* integration with the *LibUV* library.
>>
>> The library is based on *Fiber*, extending and enhancing it to provide
>> PHP developers with a full set of tools for concurrent applications.
>>
>
> Looks interesting. I understand that's not ready for review yet but
> quickly checked the code anyway. Is there some particular reason why this
> is not an extension? Think it might actually make sense to split it to two
> extensions - one for the core main stuff (that could be enabled by default)
> and then libuv optional part - similar to pdo for example. I haven't
> checked too deeply the code though so I might be missing things. Feel free
> to create a draft PR even if it's not ready. It might help to get some
> initial pre-reviews... :)
>
>
In terms of RFC, it would be good to also compare it with alternatives.
From a quick look it slightly reminded me swow (
https://github.com/swow/swow ) but I didn't really look that deeply into it
and I also don't know that much about swow so might be wrong.

--000000000000cd0c81062e1a258a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote gmail_quote_container"><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div class=3D"gma=
il_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr=
"><h3><br>A brief overview of what this RFC will cover:</h3><ol><li><strong=
>True</strong> asynchronous support for PHP core functions without addition=
al &quot;tricks.&quot;</li><li><strong>Scheduler</strong> and <strong>React=
or</strong> components, providing a C-API for PHP extensions to enable non-=
blocking I/O in plugins or core code.</li><li><strong>User-Land API</strong=
> that mirrors the C-API for PHP developers.</li><li>Basic primitives for c=
oncurrent programming, such as <strong>Channel</strong> and <strong>Iterato=
r</strong>.</li><li><strong>Built-in</strong> integration with the <strong>=
LibUV</strong> library.</li></ol><p>The library is based on <strong>Fiber</=
strong>, extending and enhancing it to provide PHP developers with a full s=
et of tools for concurrent applications.</p></div></blockquote><div><br></d=
iv><div>Looks interesting. I understand that&#39;s not ready for review yet=
 but quickly checked the code anyway. Is there some particular reason why t=
his is not an extension? Think it might actually make sense to split it to =
two extensions - one for the core main stuff (that could be enabled by defa=
ult) and then libuv optional part - similar to pdo for example. I haven&#39=
;t checked too deeply the code though so I might be missing things. Feel fr=
ee to create a draft PR even if it&#39;s not ready. It might help to get so=
me initial pre-reviews... :)</div><div><br></div></div></div></blockquote><=
div><br></div><div>In terms of RFC, it would be good to also compare it wit=
h alternatives. From a quick look it slightly reminded me swow (=C2=A0<a hr=
ef=3D"https://github.com/swow/swow">https://github.com/swow/swow</a> ) but =
I didn&#39;t really look that deeply into it and I also don&#39;t know that=
 much about swow so might be wrong.</div><div><br></div><div><br></div><div=
><br></div><div><br></div></div></div>

--000000000000cd0c81062e1a258a--