Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:18020
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Sun, 14 Aug 2005 04:37:38 +0300 (EEST)
Reply-To: Jani Taskinen <sniper@iki.fi>
To: George Schlossnagle <george@omniti.com>
cc: internals <internals@lists.php.net>
In-Reply-To: <71DDD152-EB26-4456-8541-7631BF985730@omniti.com>
Message-ID: <Pine.LNX.4.61.0508140431080.20280@arfg.argcubovn.sv>
References: <42FCE0E4.604@lerdorf.com> <42FDB870.8040807@kmit.sk>
	<8A1E0BC8-0F6C-4B70-B53E-1AE02E500F05@omniti.com>
	<Pine.LNX.4.61.0508140400100.20280@arfg.argcubovn.sv>
	<71DDD152-EB26-4456-8541-7631BF985730@omniti.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Subject: Re: [PHP-DEV] PHP 6.0 Wishlist
From: sniper@iki.fi (Jani Taskinen)

On Sat, 13 Aug 2005, George Schlossnagle wrote:

>>     Maybe this could be something that ext/session could provide.
>>     I sure can find some uses for a 'global session'.
>
> That seems like a reasonable to go.  I question it's utility a bit - how often 
> is this really useful?  For large objects (like a real cache), this isn't the 
> best place to store it, for most resources it won't work at all.  So what's a 
> typical use case for this?

     I wasn't even dreaming of using it for storing stuff like objects in it.
     As a real world example, I'd use something like that for "locking" stuff
     in the admin interface, e.g. when someone opens an item for editing,
     it's locked for all other moderators/administrators/etc...
     Of course I can accomplish that by a separate table in the database,
     but I'd like to avoid any unnecessary writes to DB whenever possible. :)

     Anyone have any other solutions to this (I'd guess quite common problem)
     I'm open for suggestions. :)

     Some other uses for a "global session" might be forums and their
     'show online users' feature.

     --Jani