Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:97324 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 7754 invoked from network); 7 Dec 2016 20:14:52 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Dec 2016 20:14:52 -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:38038] helo=es-i.jp) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 4E/3E-11772-9BD68485 for ; Wed, 07 Dec 2016 15:14:51 -0500 Received: (qmail 98270 invoked by uid 89); 7 Dec 2016 20:14:46 -0000 Received: from unknown (HELO mail-wm0-f42.google.com) (yohgaki@ohgaki.net@74.125.82.42) by 0 with ESMTPA; 7 Dec 2016 20:14:46 -0000 Received: by mail-wm0-f42.google.com with SMTP id f82so185201794wmf.1 for ; Wed, 07 Dec 2016 12:14:44 -0800 (PST) X-Gm-Message-State: AKaTC03hiRt1akQNfxY2DBd/QCZ4AyOFKzDJWiOuWfsA58FMO6REZMlYz1iedbUtzBE9udaOJRB11wpDGAC67w== X-Received: by 10.28.154.140 with SMTP id c134mr1703390wme.25.1481141677784; Wed, 07 Dec 2016 12:14:37 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.38.7 with HTTP; Wed, 7 Dec 2016 12:13:57 -0800 (PST) In-Reply-To: References: <70.0A.11772.8B1E7485@pb1.pair.com> Date: Thu, 8 Dec 2016 05:13:57 +0900 X-Gmail-Original-Message-ID: Message-ID: To: "internals@lists.php.net" Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] [RFC][VOTE] User defined session serializer From: yohgaki@ohgaki.net (Yasuo Ohgaki) Hi all, On Thu, Dec 8, 2016 at 5:07 AM, Yasuo Ohgaki wrote: >> >> I do not see the point in this RFC. > > Did you read the RFC? > It enables to write serializer by PHP script, clean and simple. It > cannot be done by save handler. > > Besides, the reason why we don't have user defined serializer is > "register_globals", the reason why we have problematic base class for > OO API save handler is "register_globals". We should get rid of > obsolete features at some point also. I thought I made it clear what the point of this RFC. "Expose serializer interface to userspace" but it seems I'm failed to do so. Those who don't understand point of this RFC, please try to write JSON/XML serializer with current APIs. You should be able to understand what's the issue. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net