Hi Stas, On Fri, Jan 22, 2016 at 7:15 AM, Stanislav Malyshev <smalys...@gmail.com> wrote: > >> We have 2 choices >> - Enforce new and correct behavior since it will not affect normal >> operation. i.e. Actual production site >> - Restore old behavior for the time being. (For this option, I prefer >> to restore only for PHP 5.6, but Ok for PHP 7.0 also. No for master) > > Since it breaks applications, the existing behavior must be restored for > both 5.6 and 7.0, unless it can be fixed ASAP. For master, a note should > be made in UPGRADING at least, but if it's substantial change that > requires applications to change then RFC would be requires I think.
The cause is logic, so it cannot be fixed unless we use bad logic. The fix will be included in my RFC ( https://wiki.php.net/rfc/precise_session_management ). BTW, it will not break application, but break tests for edge cases. I'll revert the patch if test result is good. Waiting Remi's response. Regards, -- Yasuo Ohgakid yohg...@ohgaki.net -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
