Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108249
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
In-Reply-To: <59f7df20-d89e-4076-d329-3a456bfb139a@freedom.nl>
Date: Sat, 25 Jan 2020 17:44:38 -0500
Cc: Rowan Tommins <rowan.collins@gmail.com>,
 Robert Hickman <robehickman@gmail.com>,
 PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <A544DE97-DA5D-4FC7-AEBF-75D234501FCF@newclarity.net>
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>
 <59f7df20-d89e-4076-d329-3a456bfb139a@freedom.nl>
To: Dik Takken <d.h.j.takken@freedom.nl>
Subject: Re: [PHP-DEV] Add viable long running execution model to php 8
From: mike@newclarity.net (Mike Schinkel)

> On Jan 25, 2020, at 5:35 PM, Dik Takken <d.h.j.takken@freedom.nl> =
wrote:
>=20
> Go channels are about solving problems related to true concurrency:
> Multiple threads concurrently handling requests in a single shared
> memory environment. I think Robert is talking about sequential request
> handling in a single shared memory environment.

I think you are making a distinction without a difference. I am not =
saying to exactly copy everything about channels, I am saying to learn =
aspects of architecture design from them.

If we had one long-running process that manages web-socket communication =
then sequential requests could have the ability via a constrained API to =
communicate with the long-running process to be able to use web socket =
communications.  This as opposed to allowing all PHP requests to be =
long-running.

-Mike