Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78748
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.175 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <CAAg69r=3wxiPyE5_hKOf2rY49=60a-BihsG24g9nZVrUs1iOTw@mail.gmail.com>
References: <CAAg69r=3wxiPyE5_hKOf2rY49=60a-BihsG24g9nZVrUs1iOTw@mail.gmail.com>
Date: Thu, 6 Nov 2014 06:30:57 +0900
Message-ID: <CAGa2bXaG1wLZfJfgzwZiSNC+DE5-ZPAaOd2mrFSvLUYqiyJzYQ@mail.gmail.com>
To: Damian Wadley <php@requinix.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=90e6ba613b300a62680507234edd
Subject: Re: [PHP-DEV] Lazy writing in the session, session-lock-ini, and bug #68331
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--90e6ba613b300a62680507234edd
Content-Type: text/plain; charset=UTF-8

Hi all,

On Wed, Nov 5, 2014 at 10:54 AM, Damian Wadley <php@requinix.net> wrote:

> Apparently this caused
> problems for some people as they made 68331 a few days ago.
>

Just a quick note for this. The user would like to access session
data(session handler)
regardless of data modification. I suppose it could be solved if session
has user space
"update" handler as I suggested originally.

Alternatively, session_write_close()/session_commit() may be changed, so
that it
is called unconditionally during shutdown. I have to read the code to be
sure if this is possible.

BTW, anyone know the reason why the user need to call
session_write_close()/session_commit()
unconditionally? Accounting, perhaps?

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--90e6ba613b300a62680507234edd--