Re: Re: [VOTE] Introduce session.lock, session.lazy_write and session.lazy_destory
| From: | Patrick Schaaf | Date: | Thu, 30 Jan 2014 05:44:41 +0000 |
| Subject: | Re: Re: [VOTE] Introduce session.lock, session.lazy_write and session.lazy_destory | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-71773@lists.php.net to get a copy of this message | ||
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 :)