Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:3799
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <20030807134501.9558.qmail@pb1.pair.com>
To: internals@lists.php.net
Date: Thu, 07 Aug 2003 14:45:00 +0100
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3; MultiZilla v1.4.0.4A) Gecko/20030624
MIME-Version: 1.0
References: <20030807123647.61433.qmail@pb1.pair.com> <008b01c35ce3$3bc1bcf0$1601a8c0@andreywin> <20030807131513.90932.qmail@pb1.pair.com> <20030807131928.GA19201@prp0.prp.physik.tu-darmstadt.de>
In-Reply-To: <20030807131928.GA19201@prp0.prp.physik.tu-darmstadt.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [Proposal] Idea for Application level variables
From: davey@php.net (Davey)

Stefan Walk wrote:

> On Thu, Aug 07, 2003 at 02:15:12PM +0100, Davey wrote:
> 
>>Andrey,
>>This isn't quite as transparent as $_SESSION is and $_APPLICATION would 
>>also not be a superglobal. What I would like to see at the end of this 
>>is a $_APPLICATION variable (or $_APP? some poeple complained that 
>>$_APPLICATION is too long) that behaves *exactly* like $_SESSION (in 
>>assignment etc)  except that its values are available not across 
>>sessions but across applications and instances of applications.
>>
>>- Davey
> 
> 
> Check out this one:
> http://www.turcksoft.com/en/e_mmc.htm#api

MMCache can be used as a session handler, but this still has the 
pitfalls of the other solutions.

If you were to implement $_APP(LICATION) as suggested, then it could 
indeed (in theory) use MMCache, just as $_SESSION does

- Davey