Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:47731
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain quis.cx from 82.94.237.14 cause and error)
Message-ID: <4BB59771.2050706@quis.cx>
Date: Fri, 02 Apr 2010 09:06:25 +0200
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; nl; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: Andi Gutmans <andi@zend.com>
CC: Dennis Hotson <dennis.hotson@gmail.com>, speedy <speedy.spam@gmail.com>,
        internals@lists.php.net
References: <1941231697.20100401163215@gmail.com> <g2i469956791004011604v210ad50dx89b65cd0d731cea7@mail.gmail.com> <698DE66518E7CA45812BD18E807866CE03FA7EFF@us-ex1.zend.net>
In-Reply-To: <698DE66518E7CA45812BD18E807866CE03FA7EFF@us-ex1.zend.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] php and multithreading (additional arguments)
From: jille@quis.cx (Jille Timmermans)

Op 2-4-2010 7:16, Andi Gutmans schreef
> I think that if we were ever to implement threading we would be best off
> to enable spawning worker threads that have their own context with no
> shared data (and therefore no requirement for locking). We could then
> have a message passing API between the threads.
> Advantages:
> - Real multi-threading.
> - Simple straightforward approach which doesn't require a comp. sci.
> degree to use correctly.
> - Very stable implementation.
>    
That sounds like "I want threading; because it sounds cool!". What are 
the advantages of this above multi-process?
The systemcall-overhead for message passing?

And why did nobody mention Aprils Fools yesterday; when the 
request-for-threading was sent ;)

-- Jille