Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:97448 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 29862 invoked from network); 20 Dec 2016 21:04:31 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Dec 2016 21:04:31 -0000 Authentication-Results: pb1.pair.com header.from=yohgaki@ohgaki.net; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=yohgaki@ohgaki.net; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain ohgaki.net designates 180.42.98.130 as permitted sender) X-PHP-List-Original-Sender: yohgaki@ohgaki.net X-Host-Fingerprint: 180.42.98.130 ns1.es-i.jp Received: from [180.42.98.130] ([180.42.98.130:40694] helo=es-i.jp) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 43/9B-36089-ADC99585 for ; Tue, 20 Dec 2016 16:04:28 -0500 Received: (qmail 101180 invoked by uid 89); 20 Dec 2016 21:04:22 -0000 Received: from unknown (HELO mail-wj0-f181.google.com) (yohgaki@ohgaki.net@209.85.210.181) by 0 with ESMTPA; 20 Dec 2016 21:04:22 -0000 Received: by mail-wj0-f181.google.com with SMTP id xy5so186187320wjc.0 for ; Tue, 20 Dec 2016 13:04:21 -0800 (PST) X-Gm-Message-State: AIkVDXLSi0c0n+lD0q+DP59o82m9/ou9EGFr4ha5qQ0LcCLsPrK3pcyDfktc1jZsqwmoPWqI/JXpIJULkKPwhA== X-Received: by 10.194.174.229 with SMTP id bv5mr1112987wjc.21.1482267855284; Tue, 20 Dec 2016 13:04:15 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.38.7 with HTTP; Tue, 20 Dec 2016 13:03:34 -0800 (PST) In-Reply-To: References: Date: Wed, 21 Dec 2016 06:03:34 +0900 X-Gmail-Original-Message-ID: Message-ID: To: "internals@lists.php.net" Content-Type: text/plain; charset=UTF-8 Subject: Re: [RFC][VOTE] User defined session serializer From: yohgaki@ohgaki.net (Yasuo Ohgaki) Hi all, On Mon, Dec 5, 2016 at 10:44 AM, Yasuo Ohgaki 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