Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71313
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.174 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <52DCE356.5040600@sugarcrm.com>
References: <CAGa2bXZEXx7H+atr3LK8OLLQGSd9a-6+Gey+RhPwP0d7EvTBmw@mail.gmail.com>
 <52DC905F.2080705@sugarcrm.com> <CAGa2bXbrr3CreZoaasDFWebSG-f4ai-AcTEiX9BGXZLTvjjb+Q@mail.gmail.com>
 <52DCAE75.8070401@sugarcrm.com> <CAGa2bXZxVGtFiVLnzCZ55cOY2qhoYnyvoi-MYB9ay1Pw5Dumiw@mail.gmail.com>
 <52DCD1C5.8080109@sugarcrm.com> <CAGa2bXZbrGVJxHZNKNee-jgj19XGd8_YOWJ8ufb6mNd-qJkkOg@mail.gmail.com>
 <52DCE356.5040600@sugarcrm.com>
Date: Mon, 20 Jan 2014 18:17:10 +0900
Message-ID: <CAGa2bXZpz87qUFeSAcM8TSUg5aMMri2hWAK23u4ZQzPxOrOV5Q@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e01229710abda1604f0635de0
Subject: Re: [PHP-DEV] [VOTE] Introduce session.lock, session.lazy_write and session.lazy_destory
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--089e01229710abda1604f0635de0
Content-Type: text/plain; charset=UTF-8

Hi Stas,

On Mon, Jan 20, 2014 at 5:50 PM, Stas Malyshev <smalyshev@sugarcrm.com>wrote:

> > I'll write clearly that "end users" should never enable dangerous
> > options unless
> > developer explicitly allows it. I'll also write that developers are
>
> I don't think we should provide options that need disclaimers that say
> "do not use it unless in very rare cases". If you are experienced enough
> that you need this rare case, you can implement your own session handler
> that does that. Especially given that the only use case I have seen so
> far actually does not need this feature and works just fine with much
> safer and smaller feature (session unlock, aka session_discard, aka
> session_abort).


This is feasible option.
There is session_abort() already. It's nice to have session_unlock().
I'll add session_unlock(). It requires new save handler API, but API is
modified anyway.

I understand your discussion and anxiety. People do stupid things w/o
knowing what they are doing.

Yet, I would like to have "non transaction query" like session data
handling, since there are apps that work as it should without
additional/modified code and enjoy much better performance.

I'll change voting option so that people could vote feature by feature.
 There are 3 users including me who vote to this RFC. They have to
vote again.

I'll send mail when I finish editing the RFC, please hold to vote.

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--089e01229710abda1604f0635de0--