Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71773
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain bof.de designates 80.242.145.70 as permitted sender)
To: Yasuo Ohgaki <yohgaki@ohgaki.net>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Date: Thu, 30 Jan 2014 06:44:41 +0100
Message-ID: <8644110.XYpFnEDCiN@rofl>
User-Agent: KMail/4.11.5 (Linux/3.13.0-k10-bof; KDE/4.11.5; x86_64; ; )
In-Reply-To: <CAGa2bXYERArF7-BAwyoBevRGcoqN+GS1tF0NHCq6rNigAvN_+A@mail.gmail.com>
References: <CAGa2bXZEXx7H+atr3LK8OLLQGSd9a-6+Gey+RhPwP0d7EvTBmw@mail.gmail.com> <18069656.FoN8fZuO6C@rofl> <CAGa2bXYERArF7-BAwyoBevRGcoqN+GS1tF0NHCq6rNigAvN_+A@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [PHP-DEV] Re: [VOTE] Introduce session.lock, session.lazy_write and session.lazy_destory
From: php@bof.de (Patrick Schaaf)

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.
 
best regards
  Patrick

(*) yes I remember that I suggested it in the first place, back in October :)