Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:73189
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.172 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <5324FE40.1070704@sugarcrm.com>
References: <CAPhkiZw5xWRkc=ofh-nB5ZkjfThZFkH_+pK5RZaQFLKhno7u7A@mail.gmail.com>
 <CAGa2bXZiBuw_L_ehvTZb5_UUedtbS0n4GXYUjtKix0S9DX_8KQ@mail.gmail.com> <5324FE40.1070704@sugarcrm.com>
Date: Sun, 16 Mar 2014 10:44:17 +0900
Message-ID: <CAGa2bXZQPcdWq7wmmbeJd+qb8CY9Xa-aPb+iN=OXEd7fVZYjDg@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: Andrey Andreev <narf@devilix.net>, "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e012281a4512a1404f4af734a
Subject: Re: [PHP-DEV] [RFC] Revert/extend/postpone original RFC about
 read_only, lazy_write sessions
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--089e012281a4512a1404f4af734a
Content-Type: text/plain; charset=UTF-8

On Sun, Mar 16, 2014 at 10:28 AM, Stas Malyshev <smalyshev@sugarcrm.com>wrote:

> >> 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.
> >
>
> The vote result says "yes" on "Read only, lazy write option".


Thank you Stas.
There are long discussions and I mixed with "unsafe_lock" myself...

I'll prepare the patch now and put it in github today.

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--089e012281a4512a1404f4af734a--