Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68573 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 23325 invoked from network); 19 Aug 2013 20:16:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 Aug 2013 20:16:25 -0000 Authentication-Results: pb1.pair.com header.from=johannes@schlueters.de; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=johannes@schlueters.de; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.215.10 cause and error) X-PHP-List-Original-Sender: johannes@schlueters.de X-Host-Fingerprint: 217.114.215.10 unknown Received: from [217.114.215.10] ([217.114.215.10:53487] helo=config.schlueters.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 61/08-22131-41D72125 for ; Mon, 19 Aug 2013 16:16:20 -0400 Received: from [192.168.2.20] (host-188-174-205-10.customer.m-online.net [188.174.205.10]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: johannes@schlueters.de) by config.schlueters.de (Postfix) with ESMTPSA id C8F575BB93; Mon, 19 Aug 2013 22:16:16 +0200 (CEST) To: J David Cc: Sara Golemon , PHP internals In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Date: Mon, 19 Aug 2013 22:15:57 +0200 Message-ID: <1376943357.4056.60.camel@guybrush> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Interest in a "null" SAPI for embedding? From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=) On Mon, 2013-08-19 at 14:12 -0400, J David wrote: > On Fri, Aug 16, 2013 at 9:15 PM, Sara Golemon wrote: > > Right, gotcha. I think ideally someone should put in the grunt work to do > > what you suggested: Build libphp5.so all the time, then link up > > php/mod_php5.so/etc... against that as a shared system library (which in > > turn other programs or SAPIs could link against). > > > > I'm not sure if anyone has the time and patience to do that (for its > > relatively small return), but it'd get my vote. > > That is something I would volunteer to undertake (including RFC, etc), > but in order to do so in a productive way, someone else would have to > volunteer to do the Windows portion of the work. That's well beyond > my knowledge, ability, and available development hardware. :( > > The big preliminary question for me would be, "Is there a specific > design reason why it isn't currently done this way?" PHP already > requires shlib's that depend on shlib's, so that functionality is > probably universally available, but I can't shake the suspicion that > maybe there is some has-to-be-supported platform or use case hiding at > the periphery that requires static linking. (Which could > hypothetically be addressed with a libphp5.a, but that isn't something > I've looked into at all.) On Windows we do this already. We have php.exe apache dlls with the SAPI and then php5[ts].dll. For Unix I'm not sure it is good - it makes it complex to run multiple PHP versions next to each other which is not only relevant for developers but also hosters offering multiple versions. johannes