Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:18078 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 19825 invoked by uid 1010); 14 Aug 2005 20:59:12 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 19810 invoked from network); 14 Aug 2005 20:59:12 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Aug 2005 20:59:12 -0000 X-Host-Fingerprint: 68.236.35.30 pool-68-236-35-30.phil.east.verizon.net Received: from ([68.236.35.30:8834] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id EF/D3-33075-0A0BFF24 for ; Sun, 14 Aug 2005 16:59:12 -0400 Message-ID: To: internals@lists.php.net Date: Sun, 14 Aug 2005 16:59:07 -0400 User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 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> <42FFA203.30308@lerdorf.com> <54.43.33075.77DAFF24@pb1.pair.com> In-Reply-To: <54.43.33075.77DAFF24@pb1.pair.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 68.236.35.30 Subject: Re: [PHP-DEV] PHP 6.0 Wishlist From: contact_marcos@yahoo.es (Marc Richards) Marc Richards wrote: > Rasmus Lerdorf wrote: > >> 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. >> >> >> >> I am confused. What are you proposing here? That we write a >> multi-server memory-based datastore? That's a project in itself and >> quite beyond the scope of PHP. It would seem to me like a replicated >> database setup with decent query caching solves this problem nicely. >> >> -Rasmus > > > How about an implementation with multiple possible backends ala > session.save_handler? > > It could use "files" or "apc" by default, or optionally use something > like "mm", "msession" or "mysql" depending on the user's needs. > > > Marc Oops. Hit send a little early. Just to clarify, the value of adding this extra layer of complexity would be that developers could write apps that persitently store and retrieve data at an application level without worrying about portability. It would then be up to the server admin to choose the appropriate backend based on their own requirements such as speed, platform, security, or multi-server configuration. I would envision it working in a manner very similar to how sessions work now, including the use of a user-configurable an APPLICATION_ID to prevent colisions. Marc