Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:65474 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 31397 invoked from network); 30 Jan 2013 06:46:39 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Jan 2013 06:46:39 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.163 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.163 smtp163.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.163] ([67.192.241.163:51480] helo=smtp163.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 74/34-09318-EC1C8015 for ; Wed, 30 Jan 2013 01:46:38 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp16.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 2898B407AD; Wed, 30 Jan 2013 01:46:36 -0500 (EST) X-Virus-Scanned: OK Received: by smtp16.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id D49B5407A9; Wed, 30 Jan 2013 01:46:35 -0500 (EST) Message-ID: <5108C1CA.60900@sugarcrm.com> Date: Tue, 29 Jan 2013 22:46:34 -0800 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Pierre Joye CC: PHP internals References: <5108743A.9090705@sugarcrm.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] ZTS - why are you using it? From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > Right, but they do not give up thread safety. See "Thread State and > the Global Interpreter Lock" in: > > http://docs.python.org/2/c-api/init.html That's whole different concept of thread safety. It's basically saying "you can do anything you want outside of Python engine but only one thread can do Python at the same time". If we created GIL in PHP, most of our threading problems probably would go away, but it's not likely it would be of any use for IIS or any webserver. > The TS model in php should be redesigned in the next major version, > instead of simply giving it up. Again, I'd not mind seeing this redesign, but do we have somebody who's actually going to do that? -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227