Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71778
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)
MIME-Version: 1.0
In-Reply-To: <CAGa2bXbs71-3vySXzeu8znCS56PXBPdD2K-aDuO4K-GU5OcAMw@mail.gmail.com>
References: <CAGa2bXZEXx7H+atr3LK8OLLQGSd9a-6+Gey+RhPwP0d7EvTBmw@mail.gmail.com>
	<18069656.FoN8fZuO6C@rofl>
	<CAGa2bXYERArF7-BAwyoBevRGcoqN+GS1tF0NHCq6rNigAvN_+A@mail.gmail.com>
	<8644110.XYpFnEDCiN@rofl>
	<CAGa2bXbs71-3vySXzeu8znCS56PXBPdD2K-aDuO4K-GU5OcAMw@mail.gmail.com>
Date: Thu, 30 Jan 2014 07:31:01 +0100
Message-ID: <CAJ26g5TkFAM3soxdcoPPNw6N+m8q0KuvMBfE7-dKE63pDY_UYQ@mail.gmail.com>
To: Yasuo Ohgaki <yohgaki@ohgaki.net>
Cc: internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1139b5d07eb52604f12a3351
Subject: Re: [PHP-DEV] Re: [VOTE] Introduce session.lock, session.lazy_write
 and session.lazy_destory
From: php@bof.de (Patrick Schaaf)

--001a1139b5d07eb52604f12a3351
Content-Type: text/plain; charset=ISO-8859-1

Am 30.01.2014 06:53 schrieb "Yasuo Ohgaki" <yohgaki@ohgaki.net>:

>> > > 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?

If you insist on it being short/shorter, I'd go for

unlocked_unsafe

or

unlocked

because I think, and keep thinking, that having "unlocked" there best
defuses the traditional expectation that sessions are locked during the
whole script run - thus minimizing the surprise to programmers at the PHP
level.

best regards
  Patrick

--001a1139b5d07eb52604f12a3351--