Re: [RFC][VOTE] User defined session serializer
| From: | Yasuo Ohgaki | Date: | Tue, 20 Dec 2016 21:03:34 +0000 |
| Subject: | Re: [RFC][VOTE] User defined session serializer | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-97448@lists.php.net to get a copy of this message | ||
Hi all,
On Mon, Dec 5, 2016 at 10:44 AM, Yasuo Ohgaki <yohgaki@ohgaki.net> wrote:
> 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.
This RFC is declined by 9 in favor vs 10 against.
I'm surprised by this result.
This result could be adding new PHP sadness entry. Refer to this
gist for the reason.
https://gist.github.com/yohgaki/432579e535ae97856a1227e4d47d0e2e
We must require people against RFC to explain/expose
the reason why, mustn't we? Why we must force users to
write inefficient and imprecise code?
Anyway, vote is vote.
I may address this issue again.
Thank you for voting folks!
Regards,
--
Yasuo Ohgaki
yohgaki@ohgaki.net