Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:26245
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain ilisys.com.au from 203.202.10.83 cause and error)
Message-ID: <453F2FFC.5010206@ilisys.com.au>
Date: Wed, 25 Oct 2006 17:35:56 +0800
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Antony Dovgal <antony@zend.com>
CC:  internals@lists.php.net
References: <453F2897.1050400@ilisys.com.au> <453F29ED.4050807@zend.com>
In-Reply-To: <453F29ED.4050807@zend.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] PHP user session handlers
From: glenn.richmond@ilisys.com.au (Glenn Richmond)

Done, I've just tested on PHP Version 5.2.0RC7-dev (today's snapshot)
and get the same result. The code is:

session_start();
$_SESSION['testing'] = $contents;
session_write_close();

unset($_SESSION['testing']);
   
session_start();
$newcontents = $_SESSION['testing'];
session_write_close();

There is a php file prepended to all code executions that sets up the
custom handler and it works for the first session_start, but on the
second call to session_start, I get:

*Fatal error*: session_start() [<a
href='function.session-start'>function.session-start</a>]: Failed to
initialize storage module: user (path: /tmp/php_sessions)

i.e. It still knows that it's a custom defined handler, but the
references to the functions are gone. If I make a call to
session_set_save_handler after the first session_write_close, the
problem goes away. Of course, this isn't practical for a large number of
sites.

Glenn.

Antony Dovgal wrote:
> On 10/25/2006 01:04 PM, Glenn Richmond wrote:
>> Hi guys,
>>
>> Just wondering what the status of the user-defined session handlers is?
>
> I don't think it makes any sense to ask such questions on the list,
> for the answer in most cases is "they are doing fine, thank you".
> Just grab the latest snapshot, test it and report any issues you see.
>
>> I've tested with 5.2rc4 and there is an issue that the references to the
>> user functions get erased when the user calls session_write_close or
>> session_destroy. This means that the system reverts to an alternative
>> handler.
>>
>> Any idea if this issue has been resolved or if not, how it could be
>> resolved? It basically makes large-scale user-defined session handlers
>> impossible (for general website handling). It has been discussed
>> previously, but no solution has been proposed as of yet.
>