Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:26116
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.25.124.162 as permitted sender)
Message-ID: <45389046.2050509@zend.com>
Date: Fri, 20 Oct 2006 13:00:54 +0400
User-Agent: Thunderbird 1.5.0.7 (X11/20060909)
MIME-Version: 1.0
To: Glenn Richmond <glenn.richmond@ilisys.com.au>
CC:  internals@lists.php.net
References: <45385201.7020001@ilisys.com.au> <45388B4B.8000001@zend.com> <45388DB3.5050508@ilisys.com.au>
In-Reply-To: <45388DB3.5050508@ilisys.com.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Memcache session handler
From: antony@zend.com (Antony Dovgal)

On 10/20/2006 12:49 PM, Glenn Richmond wrote:
> 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:

Yes, I understand that.
I just expected a session handler would use the existing interface to memcache instead of reinventing the wheel.
Am I wrong?

> 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?

I personally don't think it could/should be a merged into the core, 
while I'm absolutely fine with merging it to PECL/memcache.

-- 
Wbr, 
Antony Dovgal