Hi,
On Fri, Apr 9, 2021 at 5:48 PM Mohammad Eftekhari
wrote:
> Hi and thanks for the latest great features.
>
>
> Idea visualized:
>
> https://drive.google.com/file/d/1twuCTk2ssNl5damTydP-aOmOeJ5hWr9r/view?usp=sharing
>
> This is an idea and it's simple on the paper: *To run the requests coming
On 09.04.21 20:22, André Hänsel wrote:
Have you tried Roadrunner? I think your design is quite similar (identical?) to
what Roadrunner does, only that your
worker pool is managed by FPM instead of Roadrunner and that the worker exits
after serving one request - which you
*can* do with Roadrunne
Have you tried Roadrunner? I think your design is quite similar (identical?) to
what Roadrunner does, only that your
worker pool is managed by FPM instead of Roadrunner and that the worker exits
after serving one request - which you
*can* do with Roadrunner, but it's not recommended.
--
PHP Int
Hey,
I have seen this a while ago and it looks promising, however, I do have my
fair share of concerns, namely:
1. We should be able to define some sort of TTL. What happens if no request
comes for over an hour? Albeit this is *really* unlikely.
2. Why not implement a mechanism similar to `fork`
Hi and thanks for the latest great features.
Idea visualized:
https://drive.google.com/file/d/1twuCTk2ssNl5damTydP-aOmOeJ5hWr9r/view?usp=sharing
This is an idea and it's simple on the paper: *To run the requests coming
to PHP Frameworks in three phases. *
Let's say FPM pool child processes can
