Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:94250
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 157.56.110.135 as permitted sender)
To: Mike Willbanks <pencap@gmail.com>
CC: PHP internals <internals@lists.php.net>
Thread-Topic: [PHP-DEV] [RFC] Asynchronous Signal Handling (withiut TICKs and
 any additional overhead).
Thread-Index: AQHRzgHOvM0WRJjP3U6pOEm0tTlQNJ/4xGOAgAAD6tk=
Date: Fri, 24 Jun 2016 16:05:57 +0000
Message-ID: <BY2PR0201MB1784FE7823E3F5191AEAC1EEBF2E0@BY2PR0201MB1784.namprd02.prod.outlook.com>
References: <BY2PR0201MB1784EB34012B17227BEEFB21BF2E0@BY2PR0201MB1784.namprd02.prod.outlook.com>,<CALrkBjYQRrxT06JZ1JwiOf62q-MyDZrM54u7Kbh7-O1953qdOQ@mail.gmail.com>
In-Reply-To: <CALrkBjYQRrxT06JZ1JwiOf62q-MyDZrM54u7Kbh7-O1953qdOQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
received-spf: None (protection.outlook.com: zend.com does not designate
 permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative;
	boundary="_000_BY2PR0201MB1784FE7823E3F5191AEAC1EEBF2E0BY2PR0201MB1784_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Jun 2016 16:05:57.0462
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 32210298-c08b-4829-8097-6b12c025a892
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR0201MB1784
Subject: Re: [PHP-DEV] [RFC] Asynchronous Signal Handling (withiut TICKs and
 any additional overhead).
From: dmitry@zend.com (Dmitry Stogov)

--_000_BY2PR0201MB1784FE7823E3F5191AEAC1EEBF2E0BY2PR0201MB1784_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

The INI setting can be changed at run-time through ini_set(). I'll update t=
he RFC.

________________________________
From: Mike Willbanks <pencap@gmail.com>
Sent: Friday, June 24, 2016 6:50:59 PM
To: Dmitry Stogov
Cc: PHP internals
Subject: Re: [PHP-DEV] [RFC] Asynchronous Signal Handling (withiut TICKs an=
d any additional overhead).

On Fri, Jun 24, 2016 at 5:20 AM, Dmitry Stogov <dmitry@zend.com<mailto:dmit=
ry@zend.com>> wrote:
Hi internals,


Please review the RFC https://wiki.php.net/rfc/async_signals

I do not like the idea of introducing this via an INI directive, what might=
 be of value is to have a behavior on the function recommendation such that=
:

pcntl_async_signals([bool $enabled])

Without passing in the variable it could return back the current status (en=
abled or not).  This provides userland a far more flexible handling.  The I=
NI setting could cause some additional issues.  What is not clear is can th=
e INI setting be changed at runtime - so additional clarification is needed=
 there.  The main concern for this comes in when you build for multiple con=
sumers and do not control the environment.  This can cause havok especially=
 when you do need to have signals.




Thanks. Dmitry.


--_000_BY2PR0201MB1784FE7823E3F5191AEAC1EEBF2E0BY2PR0201MB1784_--