Re: Session cache, lock and write
| From: | Yasuo Ohgaki | Date: | Fri, 15 Nov 2013 22:26:25 +0000 |
| Subject: | Re: Session cache, lock and write | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-70166@lists.php.net to get a copy of this message | ||
Hi Mike,
On Fri, Nov 15, 2013 at 3:54 PM, Michael Wallner <mike@php.net> wrote:
> On Fri, 15 Nov 2013 06:33:40 +0900, Yasuo Ohgaki wrote:
>
> > Memcached/Memcache/MongoDB session save handlers already have lock
> > option.
>
> If that can be implemented at the session save handler level, why even
> bother for the files handler. Let that be as safe as possible, not as
> performant as possible.
files save handler's default behavior will not change. Only new options
will be available with this change.
By the way, mm save handler does not lock session data at all
currently. (i.e. no lock option)
It is intended to provide these features as default options for
save handlers.
session.lock = Off
is better than
abc.session_lock = On
def.session_lock = Off
ghi.session_lock = On
xyz.session_lock = Off
It's not only about locking, but caching also. We don't want
abc.session_cache, xyz.session_cache or even def.enable_session_caching,
etc.
Regards,
--
Yasuo Ohgaki
yohgaki@ohgaki.net