Re: [VOTE] Introduce session.lock, session.lazy_write and session.lazy_destory

From: Date: Mon, 20 Jan 2014 02:56:31 +0000
Subject: Re: [VOTE] Introduce session.lock, session.lazy_write and session.lazy_destory
References: 1  Groups: php.internals 
Request: Send a blank email to [email protected] to get a copy of this message
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


Thread (42 messages)

« previous php.internals (#71290) next »