Hello Rasmus, Thursday, April 1, 2010, 6:16:21 PM, you wrote:
> In any sort of Web architecture native threading in PHP just doesn't > make any sense. Imagine a real-time websockets/HTTP based server processing architecture with quick event passing from one connection to another with possibility of each web client broadcasting events to all other web clients. A simple example: web chat, and a complex one: real-time web MMO game. Now imagine a whole web server written in PHP (ie. nanoserv), say, using libevent as the network backend, running the above described real-time web implementation. Alternatively, you could perhaps even wire it into worker/event model of apache/other servers instead of rolling your own. It sounds quite powerful, and development-effort-wise cheap - out of a mere HTML preprocessor! With proper threading, this would be a piece of cake to implement in PHP, efficiently and ensuring low latency, using up all available CPU cores / resources. Without using native threads, the whole class of web architectures on both server and processing levels, viewed both separately or together, are quite a bit more hairy to implement. > 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. Yep, agreed and understood. > -Rasmus -- Best regards, speedy mailto:speedy.s...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
