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
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 [EMAIL PROTECTED] wrote:
The answer would be Application-Scope vars wish we had it in PHP
M.Saleh.E.G
97150-4779817
--
PHP General Mailing
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
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
M Saleh EG wrote:
The answer would be Application-Scope vars wish we had it in PHP
Just throw them in a database.
It's a 10-line two-function PHP script you can write in 10 minutes.
Why would you want somebody else to do that for you?
[shrug]
--
Like Music?
http://l-i-e.com/artists.htm
On Wednesday 19 January 2005 01:01, Richard Lynch wrote:
M Saleh EG wrote:
The answer would be Application-Scope vars wish we had it in PHP
Just throw them in a database.
It's a 10-line two-function PHP script you can write in 10 minutes.
Why would you want somebody else to do that
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
There would be 10s of ways of doing this I assume... depends on which
technologies and resources you have access to.
Jochem Mass said:
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
if u same serialized data into a file, and load it later unserialize,
it's all the same as session handler do
On Sun, 16 Jan 2005 18:59:44 +0100, Zouari Fourat [EMAIL PROTECTED] wrote:
but u dont need to reinitialise your variables every time the script
loads, u need just to init them once and
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
but u dont need to reinitialise your variables every time the script
loads, u need just to init them once and u get what you want wherever
you want in your files
On Sun, 16 Jan 2005 11:38:48 +0800, Xuefer Tinys [EMAIL PROTECTED] wrote:
$_SESSION is same as it use serialize/unserialize, alghough
what about using $_SESSION arrays ?
On Fri, 14 Jan 2005 19:28:24 -0500, Al [EMAIL PROTECTED] wrote:
George Schlossnagle addresses exactly your requirement in his book Advanced
PHP
Programming.
Josh Whiting wrote:
Dear list,
My web application (an online classifieds server) requires
$_SESSION is same as it use serialize/unserialize, alghough there're
some difference
On Sat, 15 Jan 2005 10:06:58 +0100, Zouari Fourat [EMAIL PROTECTED] wrote:
what about using $_SESSION arrays ?
On Fri, 14 Jan 2005 19:28:24 -0500, Al [EMAIL PROTECTED] wrote:
George Schlossnagle
George Schlossnagle addresses exactly your requirement in his book Advanced PHP
Programming.
Josh Whiting wrote:
Dear list,
My web application (an online classifieds server) requires a set of
fairly large global arrays which contain vital information that most all
the page scripts rely upon for
On 05/01/2005, at 2:39 PM, Rasmus Lerdorf wrote:
You are correct, serialization tends to be the bottleneck when it
comes to restoring large data structs. So you either avoid recreating
the data structure and just use the data directly, or use an
in-process mechanism like apc_store/apc_fetch
Rasmus Lerdorf wrote:
Robert Cummings wrote:
FWIW, I can't see how a WYW server is going to make his application run
faster. The transfer of the data he wants will still have to be
serialized and unserialized (in an optimal WYW server only unserialized)
and this is is exactly his bottleneck
Richard Lynch wrote:
Rasmus Lerdorf wrote:
Robert Cummings wrote:
FWIW, I can't see how a WYW server is going to make his application run
faster. The transfer of the data he wants will still have to be
serialized and unserialized (in an optimal WYW server only unserialized)
and this is is exactly
Why don't you just create a daemon started from the command line
(shell/DOS) and have it accept socket connections from your Web server
PHP scripts and provide a SOA (Services Oriented API) to the code that
accesses your data structures pre-loaded in memory?
Setting up a separate
Josh Whiting wrote:
However, would a single process PHP server daemon be able to
appropriately handle the incoming load from Apache, which will be
running multiple processes handling concurrent incoming requests?
I don't think you've quite got the right picture here...
When you write your
However, would a single process PHP server daemon be able to
appropriately handle the incoming load from Apache, which will be
running multiple processes handling concurrent incoming requests?
I don't think you've quite got the right picture here...
When you write your single process PHP
Hello,
on 01/04/2005 03:01 PM Josh Whiting said the following:
Why don't you just create a daemon started from the command line
(shell/DOS) and have it accept socket connections from your Web server
PHP scripts and provide a SOA (Services Oriented API) to the code that
accesses your data
On Tue, 2005-01-04 at 16:06, Josh Whiting wrote:
However, would a single process PHP server daemon be able to
appropriately handle the incoming load from Apache, which will be
running multiple processes handling concurrent incoming requests?
I don't think you've quite got the right
Robert Cummings wrote:
FWIW, I can't see how a WYW server is going to make his application run
faster. The transfer of the data he wants will still have to be
serialized and unserialized (in an optimal WYW server only unserialized)
and this is is exactly his bottleneck using an include. Actually
* Josh Whiting [EMAIL PROTECTED]:
My web application (an online classifieds server) requires a set of
fairly large global arrays which contain vital information that most all
the page scripts rely upon for information such as the category list,
which fields belong to each category, and so on.
Hello,
on 01/03/2005 02:28 PM Josh Whiting said the following:
* - Please note that I am using the Zend Accelerator (on Redhat
Enterprise with Apache 1.3) to cache the intermediate compiled PHP code.
My benchmarks (7ms+) are after the dramatic speedup provided by the
accelerator. I wouldn't even
I've only skimmed this(have to go soon), but it sounds like something
you could port the FastCGI dev library to PHP for(perhaps using SWIG).
Bare in mind that this is just from the top of my head, and is
probably irrational.
On Mon, 03 Jan 2005 16:21:35 -0200, Manuel Lemos [EMAIL PROTECTED]
26 matches
Mail list logo
