Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:73185 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 88089 invoked from network); 16 Mar 2014 01:12:48 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Mar 2014 01:12:48 -0000 Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.170 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.217.170 mail-lb0-f170.google.com Received: from [209.85.217.170] ([209.85.217.170:55574] helo=mail-lb0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 4B/C0-16948-E8AF4235 for ; Sat, 15 Mar 2014 20:12:47 -0500 Received: by mail-lb0-f170.google.com with SMTP id s7so2811434lbd.29 for ; Sat, 15 Mar 2014 18:12:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=PfdE6oxP7OTnBbKVoX0HFbK9Wuy4vdIPXuWwAEPdXEk=; b=JN44g1txWbBJVyJhwJzUm7VR55QY9/QHCa2cOIaDvMiO0pqmP2Mbljsno/oZccnXJi 4RYtUuOPdVzuAj+RRw+vym+FWsChlW2H54ZwfKkgf7O12z8rcB0lZFcfUP4y5V67ruYy 7KEZbbTuWayHyZ0eMTsXToD5ESmrAcdvuszTgAWDFE0igREX30GxIN8X/fpDzfx91gZm DKWyL8PgSMZrrXLzJTuaOHtp10ZPRG23yIcfoKv9qHoShMP9Fh4+b+WKBrftDaPD0Xoz 0MHGYwIV6Aw1cOXbgyNbgNMnJElp7GTnsjhdleruc8FtT1PIiMKR4blgMqKc8cQ52nX1 Owdg== X-Received: by 10.152.43.70 with SMTP id u6mr11320539lal.3.1394932362990; Sat, 15 Mar 2014 18:12:42 -0700 (PDT) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.112.205.73 with HTTP; Sat, 15 Mar 2014 18:12:02 -0700 (PDT) In-Reply-To: References: Date: Sun, 16 Mar 2014 10:12:02 +0900 X-Google-Sender-Auth: EUguatqjKjZWZ5VbP1V-yzhj_Kc Message-ID: To: Andrey Andreev Cc: "internals@lists.php.net" Content-Type: multipart/alternative; boundary=001a11c352a4fb5a7e04f4aeff6e Subject: Re: [PHP-DEV] [RFC] Revert/extend/postpone original RFC about read_only, lazy_write sessions From: yohgaki@ohgaki.net (Yasuo Ohgaki) --001a11c352a4fb5a7e04f4aeff6e Content-Type: text/plain; charset=UTF-8 Hi Andrey, On Sun, Mar 16, 2014 at 3:24 AM, Andrey Andreev wrote: > I'm announcing the following RFC for discussion, with the hope that it > can get through before the PHP 5.6 release: > https://wiki.php.net/rfc/session-read_only-lazy_write > > As noted in it, I don't feel like > https://wiki.php.net/rfc/session-lock-ini was handled properly. Lack > of attention to it alone is demonstrated by the fact that a total of > only 10 people have voted. I hope that this follow-up receives more > attention, so that we can avoid a potential mess. > "lazy_write" is not accepted. So you don't need to mention it in the RFC. "read_only" option is better/much faster version of "session_start(); session_commit()". If the name "read_only" is confusing, better name would be appreciated. BTW, I have to commit accepted RFC change now. Option name may be changed before release. "write short cut" is there, since it does not affect existing behavior nor save handlers at all. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --001a11c352a4fb5a7e04f4aeff6e--