Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126434
Precedence: bulk
MIME-Version: 1.0
References: <CAMW7n8CcNuttyxhtDeG1apHFVjU_9sKAhf0RG890b82Q1AnJpw@mail.gmail.com>
 <24becc76-b67f-4805-b33b-cd4f9f6d0b30@scriptfusion.com> <CAMW7n8BLE+jWsnFyAn6HcJZUzYC+Y+trpiOp2tGDony1hvE9dQ@mail.gmail.com>
 <88656d56-7bfc-4966-8fea-4b4ea883f1f1@scriptfusion.com>
In-Reply-To: <88656d56-7bfc-4966-8fea-4b4ea883f1f1@scriptfusion.com>
Date: Mon, 17 Feb 2025 21:31:57 +0200
Message-ID: <CAMW7n8BPt74jafDvSA55rZ23WLt_vLv197XW-K0uAGTOp0EfmA@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="00000000000075ce11062e5b9497"
From: edmond.ht@gmail.com (Edmond Dantes)

--00000000000075ce11062e5b9497
Content-Type: text/plain; charset="UTF-8"

>  There should be no perceptible difference between a blocking sleep(10)
and an async sleep(10), so what backwards compatibility are you referring
to?

For example, the behavior of the code below will not change. The code will
execute sequentially, and context switching will only occur when resume/
suspend is called.

However, when the Scheduler is activated, this behavior changes. Now,
calling sleep() inside a Fiber will lead to a context switch.

If the activation of the Scheduler is implicit, previously written code may
not work as the developer expects.

<?php

$fiber = new Fiber(function (): void {
    echo "Start fiber\n";
    sleep(1);
    Fiber::suspend("Paused");
    echo "Resume fiber\n";
});

$result = $fiber->start();

echo "Fiber suspended with: $result\n";

sleep(10);

$fiber->resume();

echo "Fiber finished\n";

--00000000000075ce11062e5b9497
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">&gt;=C2=A0

There should be no perceptible difference between a blocking sleep(10) and =
an async sleep(10), so what backwards compatibility are you referring to?<d=
iv><br></div><div><p>For example, the behavior of the code below will not c=
hange. The code will execute sequentially, and context switching will only =
occur when <code>resume</code>/<code>suspend</code> is called.</p><p>Howeve=
r, when the <code>Scheduler</code> is activated, this behavior changes. Now=
, calling <code>sleep()</code> inside a <code>Fiber</code> will lead to a c=
ontext switch.</p><p>If the activation of the <code>Scheduler</code> is imp=
licit, previously written code may not work as the developer expects.</p></=
div><div><br></div><div>&lt;?php<br><br>$fiber =3D new Fiber(function (): v=
oid {<br>=C2=A0 =C2=A0 echo &quot;Start fiber\n&quot;;</div><div>=C2=A0 =C2=
=A0 sleep(1);<br>=C2=A0 =C2=A0 Fiber::suspend(&quot;Paused&quot;);<br>=C2=
=A0 =C2=A0 echo &quot;Resume fiber\n&quot;;<br>});<br><br>$result =3D $fibe=
r-&gt;start();<br><br>echo &quot;Fiber suspended with: $result\n&quot;;</di=
v><div><br></div><div>sleep(10);<br><br>$fiber-&gt;resume();<br><br>echo &q=
uot;Fiber finished\n&quot;;</div></div></div>

--00000000000075ce11062e5b9497--