Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:42940 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 24696 invoked from network); 5 Feb 2009 16:37:58 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Feb 2009 16:37:58 -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 83.243.58.133 cause and error) X-PHP-List-Original-Sender: johannes@schlueters.de X-Host-Fingerprint: 83.243.58.133 mailout1.netbeat.de Linux 2.6 Received: from [83.243.58.133] ([83.243.58.133:55166] helo=mailout1.netbeat.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 1E/C5-24530-5E51B894 for ; Thu, 05 Feb 2009 11:37:58 -0500 Received: (qmail 21881 invoked by uid 89); 5 Feb 2009 16:49:58 -0000 Received: from unknown (HELO ?192.168.1.103?) (johannes%schlueters.de@93.104.114.3) by mailout1.netbeat.de with ESMTPA; 5 Feb 2009 16:49:58 -0000 To: Kalle Sommer Nielsen Cc: Terry Braun , internals@lists.php.net In-Reply-To: <2dedb8a0902050808u1c2425c6l69e1379e60b8abb6@mail.gmail.com> References: <498B01E6.2010605@talking.com> <2dedb8a0902050808u1c2425c6l69e1379e60b8abb6@mail.gmail.com> Content-Type: text/plain Date: Thu, 05 Feb 2009 17:37:53 +0100 Message-ID: <1233851873.8601.28.camel@goldfinger> Mime-Version: 1.0 X-Mailer: Evolution 2.24.3 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] adding support for PHP to a web server From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=) Hi, On Thu, 2009-02-05 at 17:08 +0100, Kalle Sommer Nielsen wrote: > Currently theres no SAPI documentation, however like Alexey said it > would probably be easier to just the cgi/fastcgi protocol. There's a chapter in Sara's book. sapi/embed is a quite simple example of an SAPI. But I agree (Fast)GI sounds like a saner way,else you'd have to provide some C wrapper giving you some APIs you can use from your Java code. Directly using PHP APIs via JNI doesn't really sound like fun. johannes