Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:42937
Return-Path: <kalle.php@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 11212 invoked from network); 5 Feb 2009 16:08:26 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 5 Feb 2009 16:08:26 -0000
Authentication-Results: pb1.pair.com header.from=kalle.php@gmail.com; sender-id=pass; domainkeys=bad
Authentication-Results: pb1.pair.com smtp.mail=kalle.php@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 72.14.220.155 as permitted sender)
DomainKey-Status: bad
X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01
X-PHP-List-Original-Sender: kalle.php@gmail.com
X-Host-Fingerprint: 72.14.220.155 fg-out-1718.google.com  
Received: from [72.14.220.155] ([72.14.220.155:48194] helo=fg-out-1718.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 45/33-24530-7FE0B894 for <internals@lists.php.net>; Thu, 05 Feb 2009 11:08:25 -0500
Received: by fg-out-1718.google.com with SMTP id e12so196996fga.23
        for <internals@lists.php.net>; Thu, 05 Feb 2009 08:08:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:sender:received:in-reply-to
         :references:date:x-google-sender-auth:message-id:subject:from:to:cc
         :content-type:content-transfer-encoding;
        bh=ZqczfsPGGTAtCyT8qM/dS2EM7jQGhYMvsvmWpnnDars=;
        b=WNGrg1C27EPSF07hjUIJ/16+dhSoAgTFWJHDEL5njhqb3pSzof+hcX4P191BdEYZFo
         keM5m/gpXu2+cc6o/mxM4VDjeyfs4tgMI3a8WkVWFKgeV//T8UuK2pTxSw6QK3hKXXSX
         FuwYSSkqxAggM6WFJ6JJom5LrQNNLQU+T12qo=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:cc:content-type
         :content-transfer-encoding;
        b=BeGZGwrO07byXfBv/NBMDGuEdpH0dmx/Ld+uJAptMg4+K8N+0uL12lzjYTsbH4dm8r
         OJGw/FGWea9d2mBGvf5vrcALZbIEK+Jf8u4fJNSJ3iXPIjFwm9XhUwsFJcMl7MOUj52u
         +doXjTKP2wl9jp73ewU4PgQxret2DxdkcvjgE=
MIME-Version: 1.0
Sender: kalle.php@gmail.com
Received: by 10.223.108.210 with SMTP id g18mr529252fap.38.1233850100345; Thu, 
	05 Feb 2009 08:08:20 -0800 (PST)
In-Reply-To: <498B01E6.2010605@talking.com>
References: <498B01E6.2010605@talking.com>
Date: Thu, 5 Feb 2009 17:08:20 +0100
X-Google-Sender-Auth: 87ea76e64b9165c9
Message-ID: <2dedb8a0902050808u1c2425c6l69e1379e60b8abb6@mail.gmail.com>
To: Terry Braun <tab@talking.com>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] adding support for PHP to a web server
From: kalle@php.net (Kalle Sommer Nielsen)

Hello

2009/2/5 Terry Braun <tab@talking.com>:
> Hello,
> I've written a small web server and I'd like to add support for php to the
> server. Could anyone direct me to documentation or examples and give me some
> sense of how hard this would be. Put another way, if I have a working PHP
> installation and a web server how do the two communicate?

Currently theres no SAPI documentation, however like Alexey said it
would probably be easier to just the cgi/fastcgi protocol.

>
> The webserver is written in javascript running on rhino which in turn runs
> on java so probably the access would be through java.
>
> Thanks
> Terry



-- 
Kalle Sommer Nielsen