Jille Timmermans wrote:
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?
Actually Andi's outline forms a nice simple base for something practical. It
simply builds on the 'background' threading required to run asynchronous
operations while not creating a unmanageable mess. But I still can't see any
need to go beyond perhaps asynchronous SQL queries.
It still requires that all the non-thread safe code is addressed first? Even if
that simply means disabling extensions that are not safe?
And why did nobody mention Aprils Fools yesterday; when the
request-for-threading was sent ;)
Because it was after noon when it was sent ;)
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
