> On Jan 25, 2020, at 5:35 PM, Dik Takken <d.h.j.tak...@freedom.nl> wrote: > > 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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
