Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:47721
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.78.25 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=subject:mime-version:content-type:from:in-reply-to:date:cc
         :content-transfer-encoding:message-id:references:to:x-mailer;
        b=Vya5OOJGaBrCJDnuJLY1D6lJhb8gqY5re3IJqr18MNVpNyMim7v67xIwlaLOIlof04
         IYgSymnsb/LURyPE8gMt9t34QzgSVXqDirEfgCBRM+zJp1Og357v0It5uyzcK/ifnJpK
         Gye1CXmbX31kgIAmT/B7KhdMHNhfI+f68sk1E=
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <4BB4E80A.3000402@zend.com>
Date: Fri, 2 Apr 2010 00:15:50 +0400
Cc: speedy <speedy.spam@gmail.com>,
 internals@lists.php.net
Content-Transfer-Encoding: quoted-printable
Message-ID: <5BAD9F0C-858B-4DE5-9303-C1FF08F19C65@gmail.com>
References: <1941231697.20100401163215@gmail.com> <4BB4E80A.3000402@zend.com>
To: Stanislav Malyshev <stas@zend.com>
Subject: Re: [PHP-DEV] php and multithreading (additional arguments)
From: indeyets@gmail.com (Alexey Zakhlestin)


On 01.04.2010, at 22:38, Stanislav Malyshev wrote:

> Hi!
>=20
>>       processing, but then the state syncing of the forked background =
processing
>>       results with the main thread requires a whole new protocol / =
switching to
>>       interprocess communication, which makes such developments =
unnecessarily
>>       hard. Threads exist for a _reason_ not only because they sound =
cool.
>=20
> Interesting thing here threads would require (at least if they are =
implemented the way C, etc. threads usually work) whole new protocol of =
synchronization too. Just think about something: do you have shared =
classes/variables/etc.?
> If you do, how you control access to them? Hello locks and the whole =
can of worms! Most people that think they can program in threads =
actually are just pushing their luck until some complex interaction =
leaves their app malfunctioning in a bizarre way and them without any =
means to debug it. I mean, you can do it right, but it's usually harder =
than it looks. Share-nothing exists for a reason too :)

Well, strictly speaking, there are [at least] 2 models which can be =
used:
1) Classical with shared resources and locking
2) STM

Anyway, do we really have to tell people "you don't need it" when they =
believe that they do?
Python has multithreading and it works reasonably good. People who know =
what they are doing can implement really brilliant solutions (think =
Tornado)
And something like GIL feels like a reasonable compromise to me.=