Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108393
MIME-Version: 1.0
References: <CAMuFt-6V24w6o8-hoPeRETCtfW25OtQ3KwdYprpYoQqpNQ2OsQ@mail.gmail.com>
 <3ca6d665-1a4f-8f7a-c82a-2e899f2e8df1@gmail.com> <CAMuFt-6Urf=7rXgR08_OsNSkBQeKVR84DisCc+2kyQXcJPuq0g@mail.gmail.com>
 <44ba543d-b6eb-888b-9ed5-0f1e9d3b53b9@gmail.com> <8E382251-AE41-4BD9-A5F8-135D11B9E10D@newclarity.net>
 <c2848f32-b06f-6711-8cbd-7fcba263ce29@gmail.com> <fd2455d3-ce1b-c699-a372-cab2eef0f280@cubiclesoft.com>
 <CAJvSBVN0ybvXsrRnw5nUdAUAeRZ9vEom=pkJ7JCsqP8qfSfx9A@mail.gmail.com>
 <CALKiJKp9TCuwRDhvBi_5dUGeQNoMo3=XcEnt_dBjFdaLDU7xtg@mail.gmail.com> <CAJvSBVOchg6t=JT9xaxp3eZOgFVoy-VvJOs+DTnoa-PrDNefSQ@mail.gmail.com>
In-Reply-To: <CAJvSBVOchg6t=JT9xaxp3eZOgFVoy-VvJOs+DTnoa-PrDNefSQ@mail.gmail.com>
Date: Tue, 4 Feb 2020 18:56:16 +0300
Message-ID: <CAMuFt-5H34gqs+iPEbH21h2eKNBipmD5se3ZaBtfYAqUgBY8zQ@mail.gmail.com>
To: Peter Bowyer <phpmailinglists@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000004876a2059dc2152f"
Subject: Re: [PHP-DEV] Add viable long running execution model to php 8
From: robehickman@gmail.com (Robert Hickman)

--0000000000004876a2059dc2152f
Content-Type: text/plain; charset="UTF-8"

On Wed, 29 Jan 2020, 7:42 pm Peter Bowyer, <phpmailinglists@gmail.com>
wrote:

> On Tue, 28 Jan 2020 at 17:12, Rowan Tommins <rowan.collins@gmail.com>
> wrote:
>
> > I'd just like to point out that those two things are orthogonal: the fact
> > that Swoole is distributed as an extension is not the reason it's
> > incompatible with your existing code, and building a similar
> implementation
> > into PHP under a different name wouldn't make the migration any easier.
> >
>
> You're absolutely right. The difference I'm thinking is that if there is
> built-in support in the language, frameworks will embrace it. At the moment
> I'd need to make my own fork to add compatibility with Swoole et al (or use
> one of the experimental but unsupported forks out there), which isn't
> attractive.
>

This was why i raised the issue. If it is covered in the core more people
are going to use it. It would be espesially good if it could be supported
within the shared hosting settings where php is commonly used.

As swoole etc have allready done good work, would it make sense to adopt
one of these as official?

>

--0000000000004876a2059dc2152f--