2016-04-19 19:54 GMT+03:00 David Zuelke <d...@heroku.com>: > I think this solution is merely a band-aid for a more profound architectural > weakness of current PHP setups, where a web server call out to the engine > (via embedding or FastCGI) to execute a script, which causes this recurring > initialization overhead in the first place. > > The future is (or should be) servers implemented fully in PHP code (e.g. > PHP-PM), just like every other comparable language (Ruby, Python, Java, ...) > already does. That also brings many other benefits, such as the ability to > handle upgrades to WebSockets in the same codebase, stream request bodies as > they're being uploaded, and so forth. > > And the performance figures that PHP-PM delivers with Symfony validate that > approach IMO. >
I agree, and developers are already discussing a common event-loop API: https://github.com/async-interop/event-loop -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
