Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71774
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.175 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <8644110.XYpFnEDCiN@rofl>
References: <CAGa2bXZEXx7H+atr3LK8OLLQGSd9a-6+Gey+RhPwP0d7EvTBmw@mail.gmail.com>
 <18069656.FoN8fZuO6C@rofl> <CAGa2bXYERArF7-BAwyoBevRGcoqN+GS1tF0NHCq6rNigAvN_+A@mail.gmail.com>
 <8644110.XYpFnEDCiN@rofl>
Date: Thu, 30 Jan 2014 14:52:54 +0900
Message-ID: <CAGa2bXbs71-3vySXzeu8znCS56PXBPdD2K-aDuO4K-GU5OcAMw@mail.gmail.com>
To: Patrick Schaaf <php@bof.de>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11349a028af42404f129adea
Subject: Re: [PHP-DEV] Re: [VOTE] Introduce session.lock, session.lazy_write
 and session.lazy_destory
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--001a11349a028af42404f129adea
Content-Type: text/plain; charset=UTF-8

Hi Patrick,

On Thu, Jan 30, 2014 at 2:44 PM, Patrick Schaaf <php@bof.de> wrote:

> On Thursday 30 January 2014 14:34:35 Yasuo Ohgaki wrote:
> >
> > > Generally a really dangerous feature. minimize_lock sounds so friendly,
> > > does
> > > not imply danger really.
> > >
> > > Alternative naming proposal: unlocked_thus_unsafe
> >
> > It sounds good idea. How about shorter name?
> >
> > unsafe_lock
>
> Well, from the user (PHP code) level it is not a lock at all. The localized
> flocking is purely for internal consistency of the individual read or write
> operation, in that case.
>
> That's why I wanted to have 'unlocked' in the name. And for such a
> dangerous
> option (*) I think that a very expressive long name would be a good fit.


I understand the reason. It's descriptive, but 3 words might be too long.
'transaction_lock' might be good enough for users who know DBMS, but it
may not be enough for others.

Does anyone have short and good name?

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--001a11349a028af42404f129adea--