Re: Re: [VOTE] Introduce session.lock, session.lazy_write and session.lazy_destory
| From: | Yasuo Ohgaki | Date: | Thu, 30 Jan 2014 09:31:05 +0000 |
| Subject: | Re: Re: [VOTE] Introduce session.lock, session.lazy_write and session.lazy_destory | ||
| References: | 1 2 3 4 5 6 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-71791@lists.php.net to get a copy of this message | ||
Hi all,
On Thu, Jan 30, 2014 at 3:31 PM, Patrick Schaaf <php@bof.de> wrote:
> 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.
>
Thank you for suggestions!
I would like to use
unlock
BTW, I've the code. It's checking fd, so it serialized :)
Thank you.
--
Yasuo Ohgaki
yohgaki@ohgaki.net