Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129033
Message-ID: <e137fc55-2137-42f9-a3d2-bc22eff1bfe4@dennis.birkholz.biz>
Date: Fri, 31 Oct 2025 23:56:53 +0100
Precedence: list
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] [RFC] Polling API
To: internals@lists.php.net
References: <CAEKnhAFZXqWH20Cy2g6-0c2V1Vd4w-N0M4xefzt6tTEp90+LqQ@mail.gmail.com>
Content-Language: de-DE, en-US
In-Reply-To: <CAEKnhAFZXqWH20Cy2g6-0c2V1Vd4w-N0M4xefzt6tTEp90+LqQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
From: php@dennis.birkholz.biz (Dennis Birkholz)

Hi Jakub,

Am 30.10.25 um 10:06 PM schrieb Jakub Zelenka:
> I would like to introduce a new polling API RFC that is part of my 
> stream evolution work:

thank you for putting this RFC forward. I missed a build-in unified 
polling API for a long time!

I just have some minor remarks:

1. Why not use a "Pollable" interface that will be implemented by 
Socket, CurlHandle, etc? That would allow to directly use the "resource 
classes" without a step in between.

(The remaining resources should be converted to classes, too, and 
implement Pollable, obviously).

2. Is there a reason why mysqli (when using async queries) is missing 
from the Future Scope list? Or did it just not come to mind?

Kind regards
Dennis