Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78914
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain bof.de designates 80.242.145.70 as permitted sender)
MIME-Version: 1.0
Date: Sat, 15 Nov 2014 08:56:26 +0100
Message-ID: <CAJ26g5RmKi50cm6m-TWB5GVCMnMkJRE8yPZrCupYwOnD3=w+Vw@mail.gmail.com>
To: Yasuo Ohgaki <yohgaki@ohgaki.net>
Cc: internals <internals@lists.php.net>, Ferenc Kovacs <tyrael@php.net>
Content-Type: multipart/alternative; boundary=001a11c11c141c76c50507e1152e
Subject: Session Lazy Write (was Re: [PHP-DEV] PHP 5.6.3 is available)
From: php@bof.de (Patrick Schaaf)

--001a11c11c141c76c50507e1152e
Content-Type: text/plain; charset=UTF-8

Yasuo,

Am 15.11.2014 02:27 schrieb "Yasuo Ohgaki" <yohgaki@ohgaki.net>:
>
> I've asked this issue on this list and there wasn't much opinion.
> I'm rather put the feature in PHP 7, since 3d party session save handler
module need to
> adopt new API to get most out of it.
>
> Since master has new code, I'll prepare new patch, hopefully soon.

I'm happy with the nothing-changed-so-dont-write stuff getting more love
and being released in PHP 7 only. We are using sessions through a small
wrapper class that does it in userlevel, i.e. we close our sessions
immediately after retrieving their values, stash the values away for later
comparison, and in a shutdown handler, see whether $_SESSION changed wrt to
that memory, and when it does, open the session again to update the values.

I'll be glad to rip out that part of the code eventually, but it works and
I can easily wait for PHP 7.

What we apparently experienced with memcache session handler in PHP 5.6.2
testing, was that sessions did not get properly unlocked - presumably
because the way we do it the session variables are never changed up-front
on the first close. Of course further access to the session then hang...

best regards
  Patrick

--001a11c11c141c76c50507e1152e--