Re: [RFC] [Vote] Asynchronous Signal Handling
| From: | Dmitry Stogov | Date: | Tue, 28 Jun 2016 16:50:51 +0000 |
| Subject: | Re: [RFC] [Vote] Asynchronous Signal Handling | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-94306@lists.php.net to get a copy of this message | ||
pcntl.async_signals=0 leads to exactly the same behavior as it was in 5.* and 7.0.
Allow manual handling and using TICKs.
pcntl.async_signals=1 - new behavior with interrupts.
Thanks. Dmitry.
________________________________
From: Nikita Popov <nikita.ppv@gmail.com>
Sent: Tuesday, June 28, 2016 19:41
To: Dmitry Stogov
Cc: PHP internals
Subject: Re: [PHP-DEV] [RFC] [Vote] Asynchronous Signal Handling
On Tue, Jun 28, 2016 at 6:16 PM, Dmitry Stogov <dmitry@zend.com<mailto:dmitry@zend.com>> wrote:
Hi internals,
The RFC has been moved into voting stage:
https://wiki.php.net/rfc/async_signals
Thanks. Dmitry.
What about Bob's suggestion to add a flag (for disabling async signals) to pcntl_signal()
instead of having a global option?
In any case, imho the default for this should be on, not off. Default "on" matches the PHP
5 behavior better than "off".
Nikita