Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:26111
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.105 cause and error)
Message-ID: <45388DB3.5050508@ilisys.com.au>
Date: Fri, 20 Oct 2006 16:49:55 +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: <45385201.7020001@ilisys.com.au> <45388B4B.8000001@zend.com>
In-Reply-To: <45388B4B.8000001@zend.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Memcache session handler
From: glenn.richmond@ilisys.com.au (Glenn Richmond)

Hi Antony,

This isn't actually part of the PECL project as I understand it. The
PECL memcache project provides a PHP interface to using a memcache
server. What I've developed is a memcache session handler  that can be
used via the php.ini file by:

session.handler = memcache

As such, it's something that could (or perhaps should) be part of the
main source tree. Is there a middle stage here? i.e. Can I provide it as
an optional compile flag in the configure script?

Glenn.

Antony Dovgal wrote:
> On 10/20/2006 08:35 AM, Glenn Richmond wrote:
>> Hi all,
>>
>> I've just been implementing a memcache session handler that allows for
>> multiple servers in a cluster to store their session data in a central
>> place. I had to make the changes in the PHP source as the user session
>> handler doesn't quite work properly (it wipes the references to the PHP
>> functions when session_write_close is called). Anyway, so it's all
>> working quite well (still undergoing testing) and it works with a main
>> memcache server and a backup as a failover. I'd like to check the code
>> back into the source tree if it's something that might be of use to the
>> general community and am told that this is the list to discuss this?
>>
>> So a couple of queries:
>>
>>     * Is this something worth checking back into the main source tree?
>>     * How do I get registered as a developer or can I provide it as a
>>       .diff to an existing developer?
>
> I guess you need to contact current PECL/memcache developers.
>