Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:26119
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.154 cause and error)
Message-ID: <453894DC.3000902@ilisys.com.au>
Date: Fri, 20 Oct 2006 17:20:28 +0800
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Andreas Korthaus <akorthaus@web.de>
CC:  internals@lists.php.net, Antony Dovgal <antony@zend.com>
References: <45385201.7020001@ilisys.com.au> <45388B4B.8000001@zend.com> <45388DB3.5050508@ilisys.com.au> <4538926C.9080800@web.de>
In-Reply-To: <4538926C.9080800@web.de>
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 Andreas,

Thanks for the suggestion - looks like a nice way to separate it from
the main source tree. I'll look at this as an option also :) I think the
one nice thing of integrating with the PECL memcache project would be
re-using the memcache library backend, but will see how we go.

Regards,

Glenn.

Andreas Korthaus wrote:
> Hi Glenn,
>
> Glenn Richmond wrote:
>> 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
>
> That's exactly what you can do with an extension. Perhaps look at
> eAccelerator for an example:
>
> http://eaccelerator.net/browser/eaccelerator/trunk/session.c
>
>> 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?
>
> I think PECL:memcache is the perfect place for such a session-handler.
>
>
> best regards
> Andreas