Re: [RFC] [Vote] Asynchronous Signal Handling
| From: | Bob Weinand | Date: | Tue, 28 Jun 2016 17:25:22 +0000 |
| Subject: | Re: [RFC] [Vote] Asynchronous Signal Handling | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-94309@lists.php.net to get a copy of this message | ||
> Am 28.06.2016 um 18:41 schrieb Nikita Popov <nikita.ppv@gmail.com>:
>
> On Tue, Jun 28, 2016 at 6:16 PM, Dmitry Stogov <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
The reason I've chosen to not pursue this:
In the next major PHP version we may remove ability of manual signal handling and corresponding
pcntl.async_signals INI directive or pcntl_async_signals() function.
Thus I don't see much sense in adding complicated logic (extra parameter) if we're anyway
going to remove that.
After all, current sync handling can be changed to add to an array and then read the triggered
signals from that array.
Thus synchronous handling can be abolished. The only reason we really needed true sync dispatching
before was it not being too reliable and relying on ticks.
Bob