Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:18071 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 2550 invoked by uid 1010); 14 Aug 2005 20:18:05 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 2535 invoked from network); 14 Aug 2005 20:18:05 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Aug 2005 20:18:05 -0000 X-Host-Fingerprint: 81.103.221.48 mta08-winn.ispmail.ntl.com Solaris 8 (1) Received: from ([81.103.221.48:51968] helo=mta08-winn.ispmail.ntl.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 12/81-33075-CF6AFF24 for ; Sun, 14 Aug 2005 16:18:04 -0400 Received: from aamta09-winn.ispmail.ntl.com ([81.103.221.35]) by mta08-winn.ispmail.ntl.com with ESMTP id <20050814201800.QWHV23002.mta08-winn.ispmail.ntl.com@aamta09-winn.ispmail.ntl.com>; Sun, 14 Aug 2005 21:18:00 +0100 Received: from [192.168.0.20] (really [81.106.213.130]) by aamta09-winn.ispmail.ntl.com with ESMTP id <20050814201800.HTDG1947.aamta09-winn.ispmail.ntl.com@[192.168.0.20]>; Sun, 14 Aug 2005 21:18:00 +0100 Message-ID: <42FFA6E4.9050104@fission.org.uk> Date: Sun, 14 Aug 2005 21:17:40 +0100 User-Agent: Debian Thunderbird 1.0.2 (X11/20050402) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jani Taskinen CC: internals References: <42FCE0E4.604@lerdorf.com> <42FDB870.8040807@kmit.sk> <8A1E0BC8-0F6C-4B70-B53E-1AE02E500F05@omniti.com> <71DDD152-EB26-4456-8541-7631BF985730@omniti.com> <42FEDAAC.3000609@prohost.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] PHP 6.0 Wishlist From: gareth@fission.org.uk (Gareth Ardron) Jani Taskinen wrote: > On Sun, 14 Aug 2005, Ilia Alshanetsky wrote: > >> If apc comes bundled then it includes apc_store() and apc_fetch() this >> is pretty much $_MEMORY with a few tweaks. > > > Yes, but that is restricted to one server installations. > I need such a 'global session' that is available with multiple > front-end servers..ie. using DB as session storage. True enough, but surely good enough for a number of users to use. The fact that you need central session storage because (I'm guessing here) your frontends are behind a handful of load balancers is something which, well, lets face it - is pretty rare as far as the average users experiance goes. Just my 2c.