Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:97343 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 31415 invoked from network); 9 Dec 2016 02:24:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Dec 2016 02:24:30 -0000 Authentication-Results: pb1.pair.com smtp.mail=yohgaki@ohgaki.net; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=yohgaki@ohgaki.net; 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:47924] helo=es-i.jp) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D8/D7-12501-AD51A485 for ; Thu, 08 Dec 2016 21:24:28 -0500 Received: (qmail 4468 invoked by uid 89); 9 Dec 2016 02:24:22 -0000 Received: from unknown (HELO mail-wj0-f176.google.com) (yohgaki@ohgaki.net@209.85.210.176) by 0 with ESMTPA; 9 Dec 2016 02:24:22 -0000 Received: by mail-wj0-f176.google.com with SMTP id tk12so3333976wjb.3 for ; Thu, 08 Dec 2016 18:24:22 -0800 (PST) X-Gm-Message-State: AKaTC03wyty4x/qelJKuM+LXWtOti3pmJvscCDiFTWh6ia+YtXma0QzAJ3JnN5aPyaqr8e5i/2Y2nNDyN1528Q== X-Received: by 10.194.174.229 with SMTP id bv5mr66898221wjc.21.1481250255876; Thu, 08 Dec 2016 18:24:15 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.38.7 with HTTP; Thu, 8 Dec 2016 18:23:35 -0800 (PST) Date: Fri, 9 Dec 2016 11:23:35 +0900 X-Gmail-Original-Message-ID: Message-ID: To: "internals@lists.php.net" Content-Type: text/plain; charset=UTF-8 Subject: [RFC][DISCUSSION] Add clean and complete session save handler interface From: yohgaki@ohgaki.net (Yasuo Ohgaki) Hi all, I about to write new RFC, but I would like to start discuss first. I sent PR that adds clean and complete session save handler interface. Older session save handler object/interfaces may be kept, but they should be deprecated because they are obsolete. There is no point making users to use them as recommended API. https://github.com/php/php-src/pull/2234 Please refer to PR for details. BTW, users will lose ability to modify session data with recommended API, requires to use obsolete API and dirty/inefficient hack to use user's own serialization if "User defined session serializer RFC" don't pass. https://wiki.php.net/rfc/user_defined_session_serializer If you would like to avoid this, please support the RFC. Thank you. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net