Hi Yasuo, I voted "no" because I don't see any advantage over using a custom session save handler, besides adding more API that partially covers custom session save handlers. This is just confusing, in my opinion, and the API can be replicated in userland with a custom session save handler decorator instead.
Greets, Marco Pivetta http://twitter.com/Ocramius http://ocramius.github.com/ On Mon, Dec 5, 2016 at 2:44 AM, Yasuo Ohgaki <yohg...@ohgaki.net> wrote: > Hi all, > > This RFC exposes session serializer interface to user space. It works > like user defined session save handler. > > Users are able to encrypt/validate session data transparently. e.g. > You can save encrypted session data to database, decrypt encrypted > data from database transparently. > > https://wiki.php.net/rfc/user_defined_session_serializer > Vote starts: 2016-12-05 Vote ends: 2016-12-19 UTC 23:59:59 > > Although we don't have consensus about number of votes to pass, I set > this RFC to require 2/3 votes. > > Questions are welcomed if you have. > Thank you for voting. > > Regards, > > -- > Yasuo Ohgaki > yohg...@ohgaki.net > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >
