Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:3816
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Reply-To: ilia@prohost.org
To: Davey <davey@php.net>,
 internals@lists.php.net
Date: Thu, 7 Aug 2003 16:54:36 -0400
User-Agent: KMail/1.5.3
References: <20030807123647.61433.qmail@pb1.pair.com> <200308071306.25443.ilia@prohost.org> <20030807203507.36982.qmail@pb1.pair.com>
In-Reply-To: <20030807203507.36982.qmail@pb1.pair.com>
Organization: Prohost.org
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-ID: <200308071654.36835.ilia@prohost.org>
Subject: Re: [PHP-DEV] [Proposal] Idea for Application level variables
From: ilia@prohost.org (Ilia Alshanetsky)

On August 7, 2003 04:35 pm, Davey wrote:
> You've hit the nail on the head! By literally copying and pasting the
> $_SESSION code over, s/_SESSION/_APPLICATION and forcing the SID to be a
> certain thing, you pretty much implement what I want. The reasons you
> cannot just wrap $_SESSION and force a SESSION SID is if you want
> SESSION vars *and* APPLICATION vars in the same script, you'll run into
> problems... cause you cannot run simulatenous sessions and you certainly
> cannot switch when you write to a different var.

I do not believe that such a functionality is required in the core of PHP. 
This maybe a very useful PECL extension if you are willing to write it. 
However, I'd consider using existing utilities like SRM, which does not seem 
to be so much of an overkill.

Ilia