On 04/01/2010 09:03 AM, speedy wrote: > Also, keep in mind that the web is slowly shifting towards real-time > communication > / streaming with emergence of Comet, HTML5 Web Sockets etc. There are already > many web > server implementations specialising in that, and PHP is _not_ their language > of choice.
The large comet implementations I know about use a high performance proxy to hold hundreds of thousands of open sockets and then they have a dispatching mechanism to route individual requests to the various backend processing engines. PHP is very much part of that picture, and again, given that the concurrency is invariably going to be high, multi-core usage is handled by your OS. In any sort of Web architecture native threading in PHP just doesn't make any sense. In single monolithic CLI apps, you could make a case for it, but that is not the sort of architecture we are going to put a significant amount of time into. -Rasmus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
