Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:10878 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 43937 invoked by uid 1010); 2 Jul 2004 21:22:38 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 43625 invoked by uid 1007); 2 Jul 2004 21:22:35 -0000 Message-ID: <20040702212235.43624.qmail@pb1.pair.com> To: internals@lists.php.net References: Date: Fri, 2 Jul 2004 14:22:34 -0700 Lines: 34 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Posted-By: 169.229.135.175 Subject: Re: Mbedthis AppWeb From: pollita@php.net ("Sara Golemon") > We've been supporting PHP4 and now PHP5 for a while and have a PHP handler > for our embedded web server. We are seeing growing interest and have quite > a few folks using this solution. > > Our goal has been to bring PHP effectively to embedded devices. Many > devices have larger memories (e.g. industrial PC devices) and a simple and > integrated packaging of PHP with an embedded web server, often into a > single static executable -- is an ideal solution. > > I wanted to take the next step and get our SAPI interface integrated into > the core PHP distribution like Apache etc. What is the process for doing > this. And no, I'm not expecting this to be in the release cut of PHP 5.0.0. ;-) > I would expect the first step would be checking your code against http://cvs.php.net/co.php/php-src/CODING_STANDARDS to be sure that it is ready for import and provide a link to the source code of sapi/Mbedthis (or whatever you've called it) so that it can be evaluated by the PHP community at large. From there, concerns can be addressed as to the usability of your sapi and it's appropriateness for inclusion in the distribution. On that note, since this sapi has a relatively small (as a percentage) applicability to PHP installations in general, I would wonder if the PECL repository could be adapted to hold SAPI implementations. To continue that thread, I've also wondered if PECL can be used for other PHP related add-ons which don't map to PHPAPI extensions. Such as a patch to add an additional opcode to the Zend lexer/parser, or implement operator overloading for objects (both items which I've applied effort to offline but have no expectation of seeing them included in the standard distribution). -Sara