Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:26247
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain ilisys.com.au from 203.161.126.20 cause and error)
Message-ID: <453F4870.4060308@ilisys.com.au>
Date: Wed, 25 Oct 2006 19:20:16 +0800
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Lukas Kahwe Smith <lsmith@php.net>
CC: Antony Dovgal <antony@zend.com>,  internals@lists.php.net
References: <453F2897.1050400@ilisys.com.au> <453F29ED.4050807@zend.com> <453F2FFC.5010206@ilisys.com.au> <453F345D.2040905@php.net>
In-Reply-To: <453F345D.2040905@php.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] PHP user session handlers
From: glenn.richmond@ilisys.com.au (Glenn Richmond)

No, it's never worked as far as I know, but it doesn't mean it's not a 
bug. The session functions shouldn't have to be reset every time 
session_write_close or session_destroy is called. It's been logged 
previously  at: http://bugs.php.net/bug.php?id=32330. It's also a 
consistent issue in varoius forums of major PHP projects.

Any idea on a solution for this one?

Regards,

Glenn.

Lukas Kahwe Smith wrote:
> Glenn Richmond wrote:
>
>> 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.
>
> And this worked in previous releases?
> I am very certain that this was the bahviour on PHP4, not sure about 
> 5.x though.
>
> regards,
> Lukas
>