Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:36517 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 82679 invoked from network); 25 Mar 2008 19:51:20 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Mar 2008 19:51:20 -0000 Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 64.233.184.232 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 64.233.184.232 wr-out-0506.google.com Received: from [64.233.184.232] ([64.233.184.232:30862] helo=wr-out-0506.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 40/CA-28012-5B759E74 for ; Tue, 25 Mar 2008 14:51:18 -0500 Received: by wr-out-0506.google.com with SMTP id 50so2784401wri.2 for ; Tue, 25 Mar 2008 12:51:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=22k0lK4tV0Eng1zKPyANZSqujzJ1Y/YCX4Fn8KLZgjU=; b=AJM6jSHGAWZsBFD+/1kRJoj3MBre0t97PiFTHAUR/8HeHAC8doggdDLnUkSVma2ocevhXvnZPx1AKzhq6wVnLQ74TnMGhoBdVg51A43gENWs06ngL60CVtGBmbDgY2xPkfect5Zhdu3JZNPFPwwZsYnEbNS48+i6s9VIdrHEbJs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=beGlkqYfPbgGp6Urf1EhcjMUL5SEJ8caUpp9tJe9S6LPQ50xnee6XZa20BIeCem3m4N6GVVDDIf5dDRmd8ZgxwUG66zzjQMNyoR1X1wazPrvxCkGMxGEZ3xpNIMxJS4lTRlW67WAJIZ/m0R2RpH/uJ3vXQdfr6iZH52CbTtxlr8= Received: by 10.141.153.17 with SMTP id f17mr3711569rvo.267.1206474674158; Tue, 25 Mar 2008 12:51:14 -0700 (PDT) Received: by 10.141.123.13 with HTTP; Tue, 25 Mar 2008 12:51:14 -0700 (PDT) Message-ID: Date: Tue, 25 Mar 2008 20:51:14 +0100 To: "Uwe Schindler" Cc: "George Wang" , internals@lists.php.net In-Reply-To: <000001c88eb0$80dbdce0$a401a8c0@VEGA> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <47E80EB9.60900@litespeedtech.com> <698DE66518E7CA45812BD18E807866CE0165A861@us-ex1.zend.net> <20080325100552.00o51usgg04oogw0@mail.litespeedtech.com> <47E93244.4060001@litespeedtech.com> <000001c88eb0$80dbdce0$a401a8c0@VEGA> Subject: Re: [PHP-DEV] Inclusion of PHP LiteSpeed SAPI in the standard PHP distribution? From: pierre.php@gmail.com ("Pierre Joye") On Tue, Mar 25, 2008 at 8:43 PM, Uwe Schindler wrote: > > > > As of php 5.3, it is possible to have a per directory configuration, > > > > either using the system php.ini or using a .htaccess-like php.ini > > > > (.user.ini). The concept is based on what you have in htscanner but > > in > > > > a much better way (same syntax than in any php.ini). The goal is to > > > > enable this feature in all SAPIs. > > > > > I am sure the new per directory configuration should work with > > LiteSpeed > > > SAPI. However, if it needs to scan each directory repeatedly for each > > > request, it will slow down PHP even further. > > > > It is cached using a user defined ttl. > > Hi Pierre, > > How do I enable another SAPIs for this per-dir ini files? How are they > named? Found no documentation about it. > I would like to upgrade my NSAPI module (Sun Webservers) for it. As Sun > Webservers do not know .htaccess files, PHP is hard to configure for > specific directories (it is possible, but you must map all ini entries as > extra parameters in the php5_execute NSAPI call, which can be made per-dir, > in the central config files). A per-dir config by "magic files" like > ".php.ini" in script folder would be good. > Is there a generic solution for SAPIs? Not yet sadly, it is on our todo for 5.3. It is now available only for fcgi but we have to provide for each sapi. We will then finally have one portable solution to configure PHP on a per directory basis. Any help is welcome, if you like to give it a try :) It should not be very hard to do it (sapi hook and move the common parts in php main code afair). I can give a hand too but definitively not in the next 2 weeks. But we have to finish it before end of April to be ready for 5.3 (~). Cheers, -- Pierre http://blog.thepimp.net | http://www.libgd.org