Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:70122
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.48 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <CAGa2bXb7hR=jkHnxrBDXnSZkN7B6cDVPj_Nve2=tWS4_AmmOKg@mail.gmail.com>
References: <CAGa2bXb7hR=jkHnxrBDXnSZkN7B6cDVPj_Nve2=tWS4_AmmOKg@mail.gmail.com>
Date: Fri, 15 Nov 2013 04:54:38 +0900
Message-ID: <CAGa2bXY9cXzRSeh9J5jaSjLe8GZjLFZQ5g4i-_ZTHBF1pAfVQw@mail.gmail.com>
To: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c34ede059ab604eb287620
Subject: Re: Session cache, lock and write
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--001a11c34ede059ab604eb287620
Content-Type: text/plain; charset=UTF-8

Hi all,

On Fri, Nov 15, 2013 at 4:42 AM, Yasuo Ohgaki <yohgaki@ohgaki.net> wrote:

> Session module can be faster in several ways.
>
> It can ignore writing session data when session data is not changed.
> It also can remove reading session data by caching as most web
> servers support keep alive. Current session save handlers lock
> session data, but it could be unlocked.
>
> There are many applications that transnational consistency of session
> data is not mandatory.
>
> Session module could have ini settings
>  - session.read_cache = int (by default 0 = no cache. 5 for 5 seconds)
>      Read cache will be updated if session data has changed.
>  - session.lock = On/Off (On by default. Some save handlers already have
> this)
>  - session.write_short_circuit = On/Off (Off by default)
>
> Users may verify save handler feature by viewing phpinfo() and
> source code level compatibility will be kept.
>
> These features boost web application performance a lot by ignoring
> session data consistency. It's just like transnational vs.
> non-transnational SQL.
>
> session.read_cache and session.lock may be consolidated since
> enabling session.read_cache disables session.lock. There are slight
> difference between them but it may be ignored.
> (With session.lock=On, writes from other web server(PHP) can be blocked
> even when session.read_cache=5, but reading session cache on the same
> keep alive session will not be blocked, for example.)
>
> Any comments?
>

I also would like to add "session deletion delay" to mitigate session
deletion
race condition by adding deletion time in session data. (i.e
session_regenerate_id(true)
may create multiple valid sessions. This can be mitigated by having this)

session.deletion_delay = int (by default 0 = delete immediately. 10 for 10
sec later)

If there is $_SESSION['__SESSION_EXPIRE__'] and expired, new session ID is
created
automatically.

I would like to hear comments for this also.

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--001a11c34ede059ab604eb287620--