Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126433
Content-Type: multipart/alternative;
 boundary="------------pPwhZ8B565gCmVVTvNODYhFc"
Message-ID: <88656d56-7bfc-4966-8fea-4b4ea883f1f1@scriptfusion.com>
Date: Mon, 17 Feb 2025 19:19:08 +0000
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] PHP True Async
To: Edmond Dantes <edmond.ht@gmail.com>
Cc: internals@lists.php.net
References: <CAMW7n8CcNuttyxhtDeG1apHFVjU_9sKAhf0RG890b82Q1AnJpw@mail.gmail.com>
 <24becc76-b67f-4805-b33b-cd4f9f6d0b30@scriptfusion.com>
 <CAMW7n8BLE+jWsnFyAn6HcJZUzYC+Y+trpiOp2tGDony1hvE9dQ@mail.gmail.com>
Content-Language: en-GB
In-Reply-To: <CAMW7n8BLE+jWsnFyAn6HcJZUzYC+Y+trpiOp2tGDony1hvE9dQ@mail.gmail.com>
From: bilge@scriptfusion.com (Bilge)

This is a multi-part message in MIME format.
--------------pPwhZ8B565gCmVVTvNODYhFc
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

On 17/02/2025 18:53, Edmond Dantes wrote:
>
> 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’t see a 
> better solution that would be optimally balanced between legacy 
> support, explicit behavior, and implementation simplicity.
>
> Have a nice day!
>
> Ed.
>
There should be no perceptible difference between a blocking sleep(10) 
and an async sleep(10), so what backwards compatibility are you 
referring to?

Bilge

--------------pPwhZ8B565gCmVVTvNODYhFc
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">On 17/02/2025 18:53, Edmond Dantes
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAMW7n8BLE+jWsnFyAn6HcJZUzYC+Y+trpiOp2tGDony1hvE9dQ@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div dir="ltr">
          <p>I forgot to mention this. There is an important <b><u>limitation</u></b>
            in how this solution behaves in the context of PHP.</p>
          <p>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 <b>backward compatibility</b> in any way.
            Calling <code>sleep(10)</code> at the beginning 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’t see a better solution that would be
            optimally balanced between legacy support, explicit
            behavior, and implementation simplicity.</p>
          <p>Have a nice day!</p>
          <p>Ed.</p>
        </div>
        <div class="gmail_quote gmail_quote_container">
          <blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
            <div> </div>
          </blockquote>
        </div>
      </div>
    </blockquote>
    <p>There should be no perceptible difference between a blocking
      sleep(10) and an async sleep(10), so what backwards compatibility
      are you referring to?</p>
    <p>Bilge<br>
    </p>
  </body>
</html>

--------------pPwhZ8B565gCmVVTvNODYhFc--