Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:68552
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error)
To: J David <j.david.lists@gmail.com>
Cc: internals@lists.php.net
In-Reply-To: <CABXB=RS6uL-d+0HbPpYxczw7jeijxu4s1TW5Lp_8fDvmafXS0w@mail.gmail.com>
References:
	 <CABXB=RS6uL-d+0HbPpYxczw7jeijxu4s1TW5Lp_8fDvmafXS0w@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Fri, 16 Aug 2013 18:55:44 +0200
Message-ID: <1376672144.3578.5.camel@guybrush>
Mime-Version: 1.0
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 Fri, 2013-08-16 at 12:36 -0400, J David wrote:
> Our solution was to develop a new pseudo-SAPI we call the null SAPI.
> All it does is build a complete libphp5.so with no SAPI-related
> structures or functions in it at all.  Then we can build our real
> embedded SAPI -- with all its extra dependencies and goofy custom I/O
> handling -- outside the PHP tree and just link to the shared library,
> rather than entangling our app's source tree and the PHP source tree.

I was successful by using embedded SAPI for that and ignoring all things
from php_embed.[ch]. Sure this gives few extra symbols and a few bytes
of unneeded code but works fine.

johannes