Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126424
Content-Type: multipart/alternative;
 boundary="------------0wHzBCvtdOm0eLLxjo1YO18X"
Message-ID: <24becc76-b67f-4805-b33b-cd4f9f6d0b30@scriptfusion.com>
Date: Sun, 16 Feb 2025 15:41:29 +0000
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] PHP True Async
To: internals@lists.php.net
References: <CAMW7n8CcNuttyxhtDeG1apHFVjU_9sKAhf0RG890b82Q1AnJpw@mail.gmail.com>
Content-Language: en-GB
In-Reply-To: <CAMW7n8CcNuttyxhtDeG1apHFVjU_9sKAhf0RG890b82Q1AnJpw@mail.gmail.com>
From: bilge@scriptfusion.com (Bilge)

This is a multi-part message in MIME format.
--------------0wHzBCvtdOm0eLLxjo1YO18X
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 14/02/2025 11:22, Edmond Dantes wrote:
>
> Good day, everyone.
>
> I would like to request permission to create an RFC dedicated to the 
> asynchronous module for PHP.
>
> Although the source code development is still in progress, a 
> significant part of it has already been written, and the initial tests 
> are working successfully. Therefore, I could start the documentation 
> process if you consider this topic relevant and interesting for the 
> community.
>
>
>       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.
>
> Have a great day!
>
> Edmond
>
Is it really necessary to have all these `Async\launchScheduler();` 
calls? Why can't the scheduler always be running, the same as it is in 
JavaScript or any other async language? Even (userland) Revolt does not 
require the event loop to be manually started.

Cheers,
Bilge

--------------0wHzBCvtdOm0eLLxjo1YO18X
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">On 14/02/2025 11:22, Edmond Dantes
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAMW7n8CcNuttyxhtDeG1apHFVjU_9sKAhf0RG890b82Q1AnJpw@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <p>Good day, everyone.</p>
        <p>I would like to request permission to create an RFC dedicated
          to the asynchronous module for PHP.</p>
        <p>Although the source code development is still in progress, a
          significant part of it has already been written, and the
          initial tests are working successfully. Therefore, I could
          start the documentation process if you consider this topic
          relevant and interesting for the community.</p>
        <h3>A brief overview of what this RFC will cover:</h3>
        <ol>
          <li><strong>True</strong> asynchronous support for PHP core
            functions without additional "tricks."</li>
          <li><strong>Scheduler</strong> and <strong>Reactor</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 concurrent programming, such as <strong>Channel</strong>
            and <strong>Iterator</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 set of
          tools for concurrent applications.</p>
        <p>Have a great day!</p>
        <p>Edmond</p>
      </div>
    </blockquote>
    <p>Is it really necessary to have all these `<span
        class="blob-code-inner blob-code-marker " data-code-marker="+"><span
          class="pl-en"><span class="pl-v">Async</span>\launchScheduler</span>();`
        calls? Why can't the scheduler always be running, the same as it
        is in JavaScript or any other async language? Even (userland)
        Revolt does not require the event loop to be manually started.<br>
      </span></p>
    <p><span class="blob-code-inner blob-code-marker "
        data-code-marker="+">Cheers,<br>
        Bilge</span></p>
    <p></p>
  </body>
</html>

--------------0wHzBCvtdOm0eLLxjo1YO18X--