Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:72538
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.173 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
Date: Thu, 13 Feb 2014 12:39:19 +0900
Message-ID: <CAGa2bXYXuQ6hhbzTMne7SgErFfKfJ01w5RquAgA4GBAAzN7hAA@mail.gmail.com>
To: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11336ba0a3091304f2417156
Subject: [VOTE] RFC: Introduce session_start() options - read_only,
 unsafe_lock, lazy_write and lazy_destroy
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--001a11336ba0a3091304f2417156
Content-Type: text/plain; charset=UTF-8

Hi all,

I almost forgot to start vote for this RFC.
This RFC is to introduce options to session_start().
Options are read_only, lazy_write, unsafe_lock and lazy_destroy.
lazy_destroy is bug fix in fact.

https://wiki.php.net/rfc/session-lock-ini
Vote: 2014/02/13 - 2014/02/20

There is no new INI. Session operations become faster and/or more reliable
in general. Exception is unsafe_lock option. It could be used at users own
risk in return of better performance. There is a little benchmark result in
the RFC to see the benefit.

The URL to the patch is mostly complete patch. I noticed there are INI
changes that should be in different RFC. I'll fix it later. If you find
something else, please let me know.

Thank you for voting!

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--001a11336ba0a3091304f2417156--