Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:70124
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain adamharvey.name designates 209.85.219.49 as permitted sender)
MIME-Version: 1.0
Sender: adam@adamharvey.name
In-Reply-To: <CAGa2bXY9cXzRSeh9J5jaSjLe8GZjLFZQ5g4i-_ZTHBF1pAfVQw@mail.gmail.com>
References: <CAGa2bXb7hR=jkHnxrBDXnSZkN7B6cDVPj_Nve2=tWS4_AmmOKg@mail.gmail.com>
 <CAGa2bXY9cXzRSeh9J5jaSjLe8GZjLFZQ5g4i-_ZTHBF1pAfVQw@mail.gmail.com>
Date: Thu, 14 Nov 2013 12:00:56 -0800
Message-ID: <CADajX4ChvbT9JtSS=ViKWUM7f=Wq0W0rF8T-G1zhw1WwdHZ_AQ@mail.gmail.com>
To: Yasuo Ohgaki <yohgaki@ohgaki.net>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Re: Session cache, lock and write
From: aharvey@php.net (Adam Harvey)

On 14 November 2013 11:54, Yasuo Ohgaki <yohgaki@ohgaki.net> wrote:
> 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 =3D int (by default 0 =3D delete immediately. 10 f=
or 10
> sec later)
>
> If there is $_SESSION['__SESSION_EXPIRE__'] and expired, new session ID i=
s
> created
> automatically.
>
> I would like to hear comments for this also.

As a nitpick, I think I'd rather this was controlled by a function
than a magic $_SESSION key, at least in userland =E2=80=94 conceptually, it=
's
simpler to explain to users if everything in $_SESSION is always
persisted and it never affects behaviour.

+1 on the idea, though.

Adam