Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:26117 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 10389 invoked by uid 1010); 20 Oct 2006 09:10:11 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 10374 invoked from network); 20 Oct 2006 09:10:11 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Oct 2006 09:10:11 -0000 Authentication-Results: pb1.pair.com smtp.mail=glenn.richmond@ilisys.com.au; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=glenn.richmond@ilisys.com.au; sender-id=unknown Received-SPF: error (pb1.pair.com: domain ilisys.com.au from 203.202.10.154 cause and error) X-PHP-List-Original-Sender: glenn.richmond@ilisys.com.au X-Host-Fingerprint: 203.202.10.154 mailx.ilisys.com.au Linux 2.6 Received: from [203.202.10.154] ([203.202.10.154:60412] helo=mailx.ilisys.com.au) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id AC/FC-27040-F6298354 for ; Fri, 20 Oct 2006 05:10:10 -0400 Received: (qmail 15826 invoked from network); 20 Oct 2006 19:10:04 +1000 Received: from unknown (HELO ?127.0.0.1?) (203.202.11.226) by mailx.ilisys.com.au with SMTP; 20 Oct 2006 19:10:04 +1000 Message-ID: <45389269.4090904@ilisys.com.au> Date: Fri, 20 Oct 2006 17:10:01 +0800 User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Antony Dovgal CC: internals@lists.php.net References: <45385201.7020001@ilisys.com.au> <45388B4B.8000001@zend.com> <45388DB3.5050508@ilisys.com.au> <45389046.2050509@zend.com> In-Reply-To: <45389046.2050509@zend.com> X-Enigmail-Version: 0.94.0.0 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) ok, sure - I just made this assumption because there's an sqlite session handler in there (from what I can see) that I wouldn't have considered standard. I'll discuss with the PECL developers. Glenn. Antony Dovgal wrote: > 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. >