Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:79581 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 85026 invoked from network); 11 Dec 2014 20:25:45 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Dec 2014 20:25:45 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.42 as permitted sender) X-PHP-List-Original-Sender: smalyshev@gmail.com X-Host-Fingerprint: 209.85.218.42 mail-oi0-f42.google.com Received: from [209.85.218.42] ([209.85.218.42:58504] helo=mail-oi0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 0A/A3-58820-8CDF9845 for ; Thu, 11 Dec 2014 15:25:44 -0500 Received: by mail-oi0-f42.google.com with SMTP id v63so4288120oia.15 for ; Thu, 11 Dec 2014 12:25:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=TX1bh2II5wU0J5ILsHh5QdqabWtX/4BqrwjctA0vf2c=; b=EyLqG+aFA1Tk9/4AWsAYyk93ppkB1uewZyrF6i4IrDLDCl8l0pRNBCCB/qk1ThSM/J PkJ0K8RDf1hSPo5mMyNa3dgQPGH0fcNc82dZHdAl9HCkecclewwQF79jnMPMFbE+kGA+ hhqX6VX45AGERuJT0lYFUfGJJx0s7k2Y0lqcUXr3MgS+YK4bfGrF6PgVEWP3AcjN1+FV OQpLToMHKp6h+T5J2Yy4oiFmyZhgImI4dbiNXEaN2FiTgdMFH7LMplW/kgWIbIUIE1Vj hJ3WK8/3e+hqQRKJEn8xEqfTQWMC/3F1FhyLg7RkzNCPzXsLsf/L1GJvY/IM2GU27lyY U8jw== X-Received: by 10.202.230.196 with SMTP id d187mr7095150oih.105.1418329541968; Thu, 11 Dec 2014 12:25:41 -0800 (PST) Received: from Stas-Air.local (108-66-6-48.lightspeed.sntcca.sbcglobal.net. [108.66.6.48]) by mx.google.com with ESMTPSA id w81sm873560oiw.10.2014.12.11.12.25.40 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 11 Dec 2014 12:25:41 -0800 (PST) Message-ID: <5489FDC0.7070304@gmail.com> Date: Thu, 11 Dec 2014 12:25:36 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: "guilhermeblanco@gmail.com" , Marc Bennewitz CC: PHP internals References: <54874642.6080508@mabe.berlin> <54875152.3060808@mabe.berlin> <54880A15.50908@gmail.com> <5489E693.1040605@mabe.berlin> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] persistent zval From: smalyshev@gmail.com (Stanislav Malyshev) Hi! > Connection pooling could be a good usage of this if we manage to get > this working again. Connection pooling is persisting external resources, usually, which can be done with little regard to zvals, since zval for resource is just a container holding an opaque pointer. A number of extensions do persistent connections without really persisting zvals. However, in many cases PHP is multiprocess, so pooling becomes kind of problematic here - it may be hard or impossible to share connections between processes, and if you have a lot of processes, keeping connection per process can become expensive. That is to say, connection pooling is a different can of worms :) -- Stas Malyshev smalyshev@gmail.com