Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:47705
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 72.14.220.153 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=date:from:reply-to:x-priority:message-id:to:cc:subject:in-reply-to
         :references:mime-version:content-type:content-transfer-encoding;
        b=tuA5Qx5pxc3hM2Gyk0rL7O+0dF/eiSXNaLacctdItYY2QwXFLvN6skh/bxqfkHrGaf
         pwsC0s0RFWbPXhdwnw7ZDIHZzc0YYGcfLwvZesIJFiIAWfO41d8bTljrnu8tKpejLBU7
         Oxc+sFSPGcVSRu6gEV9XBDPL8z3SbOaeeUfps=
Date: Thu, 1 Apr 2010 19:27:06 +0200
Reply-To: speedy <speedy.spam@gmail.com>
Message-ID: <537889361.20100401192706@gmail.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
CC: PHP Developers Mailing List <internals@lists.php.net>
In-Reply-To: <4BB4C6D5.7030004@lerdorf.com>
References: <1941231697.20100401163215@gmail.com> <4BB4BA13.2070706@lerdorf.com> <19610230188.20100401180311@gmail.com> <4BB4C6D5.7030004@lerdorf.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] php and multithreading (additional arguments)
From: speedy.spam@gmail.com (speedy)

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 wi=
th
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/e=
vent
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, e=
fficiently
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

--=20
Best regards,
 speedy                            mailto:speedy.spam@gmail.com