Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126432
Precedence: bulk
MIME-Version: 1.0
References: <CAMW7n8CcNuttyxhtDeG1apHFVjU_9sKAhf0RG890b82Q1AnJpw@mail.gmail.com>
 <24becc76-b67f-4805-b33b-cd4f9f6d0b30@scriptfusion.com>
In-Reply-To: <24becc76-b67f-4805-b33b-cd4f9f6d0b30@scriptfusion.com>
Date: Mon, 17 Feb 2025 20:53:24 +0200
Message-ID: <CAMW7n8BLE+jWsnFyAn6HcJZUzYC+Y+trpiOp2tGDony1hvE9dQ@mail.gmail.com>
Subject: Re: [PHP-DEV] PHP True Async
To: Bilge <bilge@scriptfusion.com>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary="00000000000096de20062e5b0a36"
From: edmond.ht@gmail.com (Edmond Dantes)

--00000000000096de20062e5b0a36
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I forgot to mention this. There is an important *limitation* in how this
solution behaves in the context of PHP.

Calls to PHP functions that normally block execution in the zero-Fiber do
not change their behavior. This solution has both advantages and
disadvantages. The advantage is that it does not break *backward
compatibility* in any way. Calling sleep(10) at the beginning of <?php will
cause the process to go into a wait state.

*True Async* changes the behavior of functions only if they are running
inside a Fiber with an active Scheduler.

This is yet another consequence of this architectural decision, and some
people might not like it. However, at this point, I don=E2=80=99t see a bet=
ter
solution that would be optimally balanced between legacy support, explicit
behavior, and implementation simplicity.

Have a nice day!

Ed.

>

--00000000000096de20062e5b0a36
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><p>I forgot to mention this. There is an =
important <b><u>limitation</u></b> in how this solution behaves in the cont=
ext of PHP.</p><p>Calls to PHP functions that normally block execution in t=
he zero-Fiber do not change their behavior. This solution has both advantag=
es and disadvantages. The advantage is that it does not break <b>backward c=
ompatibility</b> in any way. Calling <code>sleep(10)</code> at the beginnin=
g of <code>&lt;?php</code> will cause the process to go into a wait state.<=
/p><p><b>True Async</b> changes the behavior of functions only if they are =
running inside a Fiber with an active Scheduler.</p><p>This is yet another =
consequence of this architectural decision, and some people might not like =
it. However, at this point, I don=E2=80=99t see a better solution that woul=
d be optimally balanced between legacy support, explicit behavior, and impl=
ementation simplicity.</p><p>Have a nice day!</p><p>Ed.</p></div><div class=
=3D"gmail_quote gmail_quote_container"><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex"><div>
    <p></p>
  </div>

</blockquote></div></div>

--00000000000096de20062e5b0a36--