Hi! > - Session fails to save if it contains special chars
Session data or session variable names? If the former, it is a strange bug but certainly needs fixing. If it's the latter, it is the same exotic issue, which I suspect very small number of people actually have. Still, I'm ok with adding option to support them, as long as it does not make problems for the majority. > - Want unserialize session from session data, not from $_SESSION > - Need function generates initial session data via dession_decode These functions can be added without changing session format, but the mere existence of these requests shows us that > - Session should use plain serialize This is not a valid request, there's nothing mandating session using plain serialize. > We don't want to keep misdesigned component due to "register_globals", > don't we? Especially when the solution does not have real BC issue. We're walking in circles here. I have a number of times existence of the BC issue, yet you plainly dismiss it as "not real", and continue to talk about register_globals, which has nothing to do with it. So, to not prolong pointless discussion, here's my opinion: 1. Adding php_serializer option for session is fine for 5.5, please make a pull req for it. 2. Making it default - as long as it is not backwards-compatible - is not OK, at least before PHP 6. If you feel strongly that it must be done, the vote must be held on this subject since this change has BC implications. With this, I think I'm done discussing this subject. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
