A different but valid approach to your concerns is krakjoe/parallel (
https://github.com/krakjoe/parallel/blob/develop/README.md). Unfortunately,
NTS support is lacking, but it would be very good if the internals
collaborated with this project.
El dom., 22 de dic. de 2019 17:59, Aran Reeks escrib
Hi!
> Does this actually fit in with php's execution model of each request
> being a separate thread / process? As far as I understand this kind of
> async programming is only useful within an event-loop architecture as
> used by nodejs for example. There are things that do this for php like
We a
Whilst it'd take work on both the internals and userland sides to
implement, with so much of the web being powered by PHP, having the ability
to even construct pages in parallel could really speed things up.
In the most simplistic way, imagine rendering multiple view components on a
site in parall
I really like this idea, non-blocking IO via asynchronous operations in
PHP would be amazing.
I am running into an issue right now where I want to listen to several
different socket streams for data. One example of this would be:
Open socket AWait for dataClose socket AOpen socket BWait for dat
>
> Does this actually fit in with php's execution model of each request
> being a separate thread / process?
I can see this being useful, when AJAX-querying an endpoint that has to do,
in turn, 2 or more API calls or other async jobs to build its response.
(although async HTTP requests are alre
Does this actually fit in with php's execution model of each request
being a separate thread / process? As far as I understand this kind of
async programming is only useful within an event-loop architecture as
used by nodejs for example. There are things that do this for php like
ReactPHP, but it i
