On 27/01/2020 15:50, Larry Garfield wrote:
I want to point out that there's 2 or 3 very different use cases and
models being discussed in this thread, and it's important to keep them
separate:
[...]
Can I add another that's been mentioned in passing:
4. A mechanism for working with WebSockets. This doesn't actually
require a different process model (although it would undoubtedly benefit
from one, in terms of system resources), but does require a new way to
talk to the web server / network (a new kind of "SAPI"). I can't think
of a fundamental reason why php-fpm couldn't leave a process running
that was connected as one end of a web socket, but doing so would be
pretty useless if there was no API to send and receive data over that
socket.
Regards,
--
Rowan Tommins (né Collins)
[IMSoP]
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
