Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126690
Precedence: bulk
MIME-Version: 1.0
References: <bb7a9f8f-0422-45e5-b4fc-f5757add92b4@app.fastmail.com>
 <CAMW7n8BnzL7d0bd_Y_jGOmyWegKQpm-FzrVFRCcDe=bNFZpi+A@mail.gmail.com>
 <08c8ad0b-e8f4-46e3-99f0-b80748d40b89@app.fastmail.com> <07973EAE-2D83-47A8-8FA0-84286C77C02B@rwec.co.uk>
 <48d66433-3ae9-4895-8361-7c81a0a3670d@app.fastmail.com> <be7cb263-93a1-4bd8-9416-ae4d3e0bafe6@rwec.co.uk>
 <dbce8889-016a-4c59-864c-d8fdec895adc@app.fastmail.com> <CAM0Ccxh=bydoDEHBAV+Gb1_86HJjwhW06kzEsdRiMh93k1F7oA@mail.gmail.com>
 <8599eb8b-d4a3-4cb8-899a-25b134e0d64d@gmail.com> <D73BCCC4-3547-45B4-84AD-A5FD6569D43C@rwec.co.uk>
 <74c4c726-63aa-44e0-84c9-840e13a65a4f@gmail.com> <77DC5F50-531D-49E8-8BE2-504A19CB5FFD@rwec.co.uk>
 <676e36e4-0b84-4d8c-b3db-2998831cd79d@gmail.com> <510B8EF1-9D07-41A8-9EA0-7D99CF7BFC91@rwec.co.uk>
 <bccf099c-55cf-4701-89eb-c26144696eac@gmail.com> <4690cff0-7a48-4fe0-8310-688be253f976@gmail.com>
 <CAMW7n8DTVPkA0qk30TCf1+L3Rmooyt5eEMco+=ds_TX3fEXn-Q@mail.gmail.com>
 <4871b2e4-353e-424f-92b9-7e2bb753bafa@gmail.com> <CAMW7n8Dzin0sYioWFCJHOfaLASLwuSggijV2=2qQA5tO4a0itA@mail.gmail.com>
 <7D224BD3-2FF7-45E8-8D90-C9AEDC80DD4F@gmail.com>
In-Reply-To: <7D224BD3-2FF7-45E8-8D90-C9AEDC80DD4F@gmail.com>
Date: Mon, 10 Mar 2025 13:13:27 +0200
Message-ID: <CAMW7n8DbLAp+8FHWUEEaCzu0H2MLzYBntPR_erO2G7Uprmzz2A@mail.gmail.com>
Subject: Re: [PHP-DEV] PHP True Async RFC
To: Daniil Gentili <daniil.gentili@gmail.com>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary="00000000000061739e062ffb104f"
From: edmond.ht@gmail.com (Edmond Dantes)

--00000000000061739e062ffb104f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

>
>  Sure:
>

Yeah, this is a Watcher, a periodic function that is called to clean up or
check something. Yes, it=E2=80=99s a very specific pattern. And of course, =
the
Watcher belongs to the service. If the service is destroyed, the Watcher
should also be stopped.

In the context of this RFC, it's better to use the Async\Interval class.

>
>  contains multiple examples of tasks of the same kind in my own library
(ping loops to keep connections alive,
> read loops to handle updates (which contain vital information needed to
keep the client running correctly) in the background, etc...), all started
on
> __construct when initialising the library, and stopped in __destruct when
they are not needed anymore.
>

Thank you, I will read it.

--

Ed.

--00000000000061739e062ffb104f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>&gt;<br>&gt;=C2=A0

Sure:<br>&gt;</div><div><br></div><div>Yeah, this is a Watcher, a periodic =
function that is called to clean up or check something. Yes, it=E2=80=99s a=
 very specific pattern. And of course, the Watcher belongs to the service. =
If the service is destroyed, the Watcher should also be stopped.</div><div>
<p>In the context of this RFC, it&#39;s better to use the <code>Async\Inter=
val</code> class.</p><p>&gt;=C2=A0<br>&gt;=C2=A0

contains multiple examples of tasks of the same kind in my own library (pin=
g loops to keep connections alive, <br>&gt; read loops to handle updates (w=
hich contain vital information needed to keep the client running correctly)=
 in the background, etc...), all started on <br>&gt; __construct when initi=
alising the library, and stopped in __destruct when they are not needed any=
more.<br>&gt;=C2=A0</p><p>Thank you, I will read it.</p><p>--</p><p>Ed.</p>=
</div></div>

--00000000000061739e062ffb104f--