Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:6261 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 72801 invoked by uid 1010); 7 Dec 2003 08:01:49 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 72777 invoked by uid 1007); 7 Dec 2003 08:01:49 -0000 To: internals@lists.php.net Date: Sun, 07 Dec 2003 00:03:46 -0800 User-Agent: Pan/0.13.3 (That cat's something I can't explain) Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Posted-By: 209.180.205.165 Subject: SAPI documentation From: mob@mbedthis.com ("Michael O'Brien") Is there any documentation regarding the SAPI interface? I'm writing a SAPI module so that I can run PHP in a new embedded web server. Why, do I want to do this? Our server is designed for embedding in applications or devices and is a fast, multi-threaded, secure, portable, small-footprint web server that uses an apache configuration file format. It really is like a small, embeddable Apache. For devices or applications that want their own in-process personal web server, our server Mbedthis AppWeb is ideal. I want to support PHP in an embedded fashion but am struggling to find documentation on the SAPI interface. I can probably work it out from the code, but there don't seem to be pointers about what are the expectations by PHP on the SAPI module. Also, there seems to be quite a bit of diversity in the level of support offered by existing SAPI handlers. Any help or pointers to existing information will be appreciated. Michael O'Brien Lead Architect http://www.mbedthis.com