Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81499
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.174 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <CAGa2bXb1xnOkYtiwonDU+HxUR0JKxi05TANRcgLh9-6ALR97tg@mail.gmail.com>
References: <CAGa2bXb1xnOkYtiwonDU+HxUR0JKxi05TANRcgLh9-6ALR97tg@mail.gmail.com>
Date: Sun, 1 Feb 2015 05:30:42 +0900
Message-ID: <CAGa2bXbYAuhYAYyyPKmpK2idEX1QAgqxtz7Jg5KeHcn=W8=1Pw@mail.gmail.com>
To: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c1257eb7569a050df89ad6
Subject: Re: Session: More strict session data management
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--001a11c1257eb7569a050df89ad6
Content-Type: text/plain; charset=UTF-8

Hi all,

On Sat, Jan 31, 2015 at 11:44 AM, Yasuo Ohgaki <yohgaki@ohgaki.net> wrote:

> As I described already, current session management is lazy to delete
> obsolete
> session data. New behavior is much stricter than now and there is no
> exposed
> internal data to users(script). The "hidden" timestamp only exists in
> obsolete
> session data. New behavior requires less GC also.
>

Current session manager is lazy for expiration also. The same method,
"hidden"
timestamp, can be used for housekeeping.

If the timestamp is updated always, "lazy_write" option is spoiled. To
prevent that,
last modified time updates could be done with longer resolution, i.e.
Update timestamp
by every minute, not second.

With this, GC is only need for true GC. i.e. GC will not be used to expire
session data.
Therefore, GC may be done once a day, for example.

Any comment?

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--001a11c1257eb7569a050df89ad6--