Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71290
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.115 as permitted sender)
Message-ID: <52DC905F.2080705@sugarcrm.com>
Date: Sun, 19 Jan 2014 18:56:31 -0800
Organization: SugarCRM
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Yasuo Ohgaki <yohgaki@ohgaki.net>, 
 "internals@lists.php.net" <internals@lists.php.net>
References: <CAGa2bXZEXx7H+atr3LK8OLLQGSd9a-6+Gey+RhPwP0d7EvTBmw@mail.gmail.com>
In-Reply-To: <CAGa2bXZEXx7H+atr3LK8OLLQGSd9a-6+Gey+RhPwP0d7EvTBmw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [VOTE] Introduce session.lock, session.lazy_write and
 session.lazy_destory
From: smalyshev@sugarcrm.com (Stas Malyshev)

Hi!

> Vote period: 2014/01/20 - 2014/01/30
> https://wiki.php.net/rfc/session-lock-ini
> 
> New comments and questions are welcomed.

I see there are three proposals there, but only one vote. E.g. I think
unlocked sessions are not a good idea, but lazy write may be ok (btw,
interaction between no-lock and lazy write can lead to completely
undebuggable scenarios when same data by same code sometimes are written
and sometimes are not depending on session state). I'm not sure I even
understand what lazy_destroy does - if the data is deleted then it's
deleted, how can it be accessible and why?

Also, do I understand correctly that the options would apply only to
files module? If so, why they under session.* and not session.files.* or
something to emphasize that if you're not using files module it doesn't
do anything?
-- 
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227