Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:73768
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.83.46 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <B0229AED-7EE6-4DEA-8336-50271803D115@gmail.com>
References: <CAPRqa+F26Ez3aEYzZU=8fwVEAg8tVnfWBJw+XAbW3tuUVomyyg@mail.gmail.com>
	<B0229AED-7EE6-4DEA-8336-50271803D115@gmail.com>
Date: Thu, 24 Apr 2014 01:30:00 +0300
Message-ID: <CAPRqa+EPiTC=XFfR9yOO=P5YsjHXED0Tj1tK-mVB_6+Y6RK2Pg@mail.gmail.com>
To: Alexey Zakhlestin <indeyets@gmail.com>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary=001a1132f658e5a1ef04f7bd455f
Subject: Re: [PHP-DEV] [FPM] Reused PHP script as daemon process
From: park.framework@gmail.com (Park Framework)

--001a1132f658e5a1ef04f7bd455f
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I simplified the example, it is possible to discuss in detail the API
There are two options, a high-level API abstraction from SAPI or low tier
API which depends on the SAPI

Abstract API
spl_server_loop(callable $name)
The infinite receiving new requests and run custom callable.

PHP send response to the client automatically, all the user response
headers and body (ob_get_contents()).
After each iteration makes ob_clean().

Sample:
<?php

$callable =3D function()
{
 MyFrameWork::run();
}

// This code execute once
MyFrameWork::init($config);
//...

// This infinite receiving new requests and run custom callable
spl_server_loop($callable);

?>

Historically that PHP developers are abstracted from SAPI.
Continue the practice for daemon process script.

Or use SAPI
fastcgi_handle_request(callable $name)
fastcgi_parse_request($input_stream_or_string);
fastcgi_encode_response($code, $headers, $body);

But then your code will run on only one SAPI, such work as Apache module,
this code can not.
The meaning of this API to allow the user complete control processes
without the possibility of transfer to other SAPI



2014-04-22 14:12 GMT+03:00 Alexey Zakhlestin <indeyets@gmail.com>:

>
> On 22 Apr 2014, at 02:27, Park Framework <park.framework@gmail.com> wrote=
:
>
> > Add, function fastcgi_handle_request(callable $name) for reused script =
as
> > daemon process.
> >
> > With each new request, all superglobals variables ($_GET, $POST,
> $_COOKIE,
> > $_SERVER, ...) with new values from current =E2=80=8B=E2=80=8Brequest.
>
> Exposing FastCGI lib to userland is something we already were talking
> about, but I don=E2=80=99t think your choice of API is good.
>
> Something like this would be much cleaner:
>
>     $data =3D fastcgi_parse_request($input_stream_or_string);
>
> Then, you can call your handler manually, and:
>
>     echo fastcgi_encode_response(200, ['hea' =3D> ['de', 'rs']], $body);
>
> lower-level functions could be useful too (for partial answers, etc.)
>
> --
> Alexey Zakhlestin
> CTO at Grids.by/you
> https://github.com/indeyets
> PGP key: http://indeyets.ru/alexey.zakhlestin.pgp.asc
>
>
>
>

--001a1132f658e5a1ef04f7bd455f--