Posted by Jochem Maas on 01/18/05 18:26

M Saleh EG wrote:
> What I mean by Application-Scope variables is variables that can be
> available for the Application or Web-Application all the time after
> starting the application by a trigger. After having the triger fired
> those Application-Scope Variables, Datastructures, Object, and
> refrences would be available for all the requests. That's how I'd
> equate persistant PHP-Applications to having Application-Scope PHP
> variables.
>
> A lame Example to illustrate the purpose of Application-Scope
> variables would be the persistant DB connections. Not 100% the same
> but it's for the same purpose
>
> So if you could have a huge object persistant( Application-Scope
> object ) that does alot of work for you then that object is a PHP
> persistant application which I call Application-Scope var or object !
>
> Hope that clears it out.
>

firstly this goes against the basic principle of 'SHARE NOTHING' that
php is based on - so I doubt that the basic php environment will be
changed to accomodate such a feature any time soon.

.... secondly there is something like this out called SRM (Script Running
Machine) which gives the same sort of functionality but in a different
way (i.e. 'application scope' vars are not part of the script itself but
run in a 'script server') - written by Direck Rethans (among others):
try the following keywords:

PHP + SRM + Bananas (+ Rethans)

Maybe it helps you.

>
> On Tue, 18 Jan 2005 11:10:29 +0100, Zouari Fourat <fourat@gmail.com> wrote:
>
>>can u explain a bit more : The answer would be Application-Scope
>>vars.... wish we had it in PHP
>>
>>On Tue, 18 Jan 2005 02:42:46 +0400, M Saleh EG <m.saleh.eg@gmail.com> wrote:
>>
>>>The answer would be Application-Scope vars.... wish we had it in PHP
>>>
>>>M.Saleh.E.G
>>>97150-4779817
>>>
>>>--
>>>PHP General Mailing List (http://www.php.net/)
>>>To unsubscribe, visit: http://www.php.net/unsub.php
>>>
>>>
>>
>
>

[Back to original message]