Hi! > Offending features may be disabled/changed by INI settings. I think it ok > to say pretty much no BC issue.
I think this approach will lead us into problems. "It may be disabled by INI setting" does not mean the problem does not exist (and btw not everything that changes can be disabled AFAIR). Most BC breaks have workarounds, but they still are BC breaks. Moreover, some of the changes are default changes, which means basically users will have to undo what this RFC does - if we think they'd have to do it, why change it in the first place? I also feel that sheer size of this RFC, the fact that it tried to fix many unrelated issues, and amount of changes it brings leads to the situation where people don't really discuss it properly but instead rely on claims in the RFC that everything is fine, because it is very hard to properly consider changes of this size with this many moving parts. At least the discussion on the list was rather scarce as far as I can see. > The difference that user/3rd party save handlers will see is an additional > array in session data. The additional array should not cause any problems > with session save handlers. The change is not limited to additional data. This additional data is active - it controls how sessions are supposed to behave. All these need to be updated when something happens, all these need to be checked, validated and user for various logic on various stages of session lifetime. So saying "it's just some additional data, nothing of it" is not true - it's not just data. Maybe everything is still OK with the session handlers - but this needs to be thoroughly verified, it does not come for free. -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
