Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:47704 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 17126 invoked from network); 1 Apr 2010 16:21:37 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Apr 2010 16:21:37 -0000 Authentication-Results: pb1.pair.com smtp.mail=rasmus@lerdorf.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=rasmus@lerdorf.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lerdorf.com from 209.85.160.42 cause and error) X-PHP-List-Original-Sender: rasmus@lerdorf.com X-Host-Fingerprint: 209.85.160.42 mail-pw0-f42.google.com Received: from [209.85.160.42] ([209.85.160.42:44344] helo=mail-pw0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C5/00-16887-018C4BB4 for ; Thu, 01 Apr 2010 11:21:37 -0500 Received: by pwi8 with SMTP id 8so392109pwi.29 for ; Thu, 01 Apr 2010 09:21:33 -0700 (PDT) Received: by 10.140.248.18 with SMTP id v18mr652306rvh.295.1270138585204; Thu, 01 Apr 2010 09:16:25 -0700 (PDT) Received: from [192.168.200.22] (c-98-234-184-167.hsd1.ca.comcast.net [98.234.184.167]) by mx.google.com with ESMTPS id p1sm3898982rvq.16.2010.04.01.09.16.23 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 01 Apr 2010 09:16:24 -0700 (PDT) Message-ID: <4BB4C6D5.7030004@lerdorf.com> Date: Thu, 01 Apr 2010 09:16:21 -0700 User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.10pre) Gecko/20100330 Shredder/3.0.5pre MIME-Version: 1.0 To: speedy CC: PHP Developers Mailing List References: <1941231697.20100401163215@gmail.com> <4BB4BA13.2070706@lerdorf.com> <19610230188.20100401180311@gmail.com> In-Reply-To: <19610230188.20100401180311@gmail.com> X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] php and multithreading (additional arguments) From: rasmus@lerdorf.com (Rasmus Lerdorf) 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