Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:65500 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 85104 invoked from network); 30 Jan 2013 12:58:00 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Jan 2013 12:58:00 -0000 Authentication-Results: pb1.pair.com header.from=bas@tobin.nl; sender-id=pass; domainkeys=good Authentication-Results: pb1.pair.com smtp.mail=bas@tobin.nl; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain tobin.nl designates 208.97.132.83 as permitted sender) DomainKey-Status: good X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: bas@tobin.nl X-Host-Fingerprint: 208.97.132.83 caiajhbdcaid.dreamhost.com Windows 98 (1) Received: from [208.97.132.83] ([208.97.132.83:49435] helo=homiemail-a37.g.dreamhost.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F1/6E-09318-7D819015 for ; Wed, 30 Jan 2013 07:58:00 -0500 Received: from homiemail-a37.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a37.g.dreamhost.com (Postfix) with ESMTP id F0FAD20806C; Wed, 30 Jan 2013 04:57:56 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=tobin.nl; h=subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to; q=dns; s=tobin.nl; b=DCgzvJmLK1XMmh0P I2C+BwazU47CRyq27EpjSNT9FihG2ImjMyt7h5Fk9HO4eTSSPUFSAgP/+wwpLWup 0oquufhYR41k6L5Tk71Glmawtm2ISZ325diXE8UVKE6RIHM+UrMxsj2ka6+JhFOu j7fnGPiILA7xBSG656g2yEwg4aY= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=tobin.nl; h=subject :mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=tobin.nl; bh=YPq/R87XmC6EBeIkWT+YWxrW0fM=; b=cYBNqhsz0YRa4v5H9rjMiGw1DyJY ZYnATEVKCQYakYkC9J2fJdTEMWyQBL4I8gaMzsmyI+4uxe0olFwJOvcl9hOvWCY4 bfBd+sd78p4IA3kbukZDqnMB5xq2MZxOxCgFq/MzREja9IC8lfBAq+8mQAj0rdvR 9UqOqJ5xZUCx118= Received: from [192.168.1.11] (82-171-216-38.ip.telfort.nl [82.171.216.38]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: bas@tobin.nl) by homiemail-a37.g.dreamhost.com (Postfix) with ESMTPSA id 5D84620806B; Wed, 30 Jan 2013 04:57:56 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii In-Reply-To: Date: Wed, 30 Jan 2013 13:57:53 +0100 Cc: PHP internals Content-Transfer-Encoding: quoted-printable Message-ID: References: <5108743A.9090705@sugarcrm.com> <4d977bab18152b2e86d968f4db9d12ef@mail.gmail.com> <9DB107EF-A5CE-4CF5-84A1-7E2D733B4089@tobin.nl> To: Zeev Suraski X-Mailer: Apple Mail (2.1283) Subject: Re: [PHP-DEV] ZTS - why are you using it? From: bas@tobin.nl (Bas van Beek) Op 30 jan. 2013, om 13:42 heeft Zeev Suraski het volgende geschreven: >> -----Original Message----- >> From: Bas van Beek [mailto:bas@tobin.nl] >> Sent: Wednesday, January 30, 2013 2:29 PM >> To: Zeev Suraski >> Cc: Pierre Joye; Stas Malyshev; PHP internals >> Subject: Re: [PHP-DEV] ZTS - why are you using it? >>=20 >> Hi Guys, >>=20 >> As a heavy user of ZTS in multi threaded C/C++ applications, here are = my > $0.02. >>=20 >> Removing ZTS would be a bad idea for all those custom multi-threaded >> applications out there that allow some form of internal/embedded PHP >> scripting. These applications are not web-servers but do make use of > threads for >> reasons of their own. Building a FastCGI set-up would be out of the > question if >> these apps are deployed customer / client side and need concurrent = PHP > script >> runs. >>=20 >>> Based on the feedback on this thread, I think we should instruct = users >>> that using thread-safe versions of PHP is slower, and that actually >>> putting thread-safe PHP inside a multithreaded server is not a very >>> reliable solution. We should recommend FastCGI/fpm instead. We >>> should do that tomorrow morning (figuratively speaking). >=20 > In case I wasn't sufficiently clear, I'm talking about putting PHP = inside > a *multithreaded web server*, not being a good idea. The use case you > specify is exactly the use case for keeping ZTS support in the code... >=20 > Zeev >=20 > --=20 > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php >=20 Yes I did get that and my response to your post was not meant as an = argument against those points but more as an addition. I just wanted to = re-enforce that ZTS has it's purpose and we should be careful about = which signals we give to the PHP user-land and extension developer = community as most of the previous posts to this thread seemed to discard = usefulness of ZTS all together as if the only important use case is = running PHP code on a web server. PHP is so much more than that and I do = not want to see PHP developers exclude or forget about these other use = cases because prominent people in the PHP community make blunt = statements as the above topic implies. Bas van Beek