9

Okay, so I'm relatively naive in my knowledge of the PHP VM and I've been wondering about something lately. In particular, what the request lifecycle looks like in PHP for a web application. I found an article here that gives a good explanation, but I feel that there has to be more to the story.

From what the article explains, the script is parsed and executed each time a request is made to the server! This just seems crazy to me!

I'm trying to learn PHP by writing a little micro-framework that takes advantage of many PHP 5.3/5.4 features. As such, I got to thinking about what static means and how long a static class-variable actually lives. I was hoping that my application could have a setup phase which was able to cache its results into a class with static properties. However, if the entire script is parsed and executed on each request, I fail to see how I can avoid running the application initialization steps for every request servered!

I just really hope that I am missing something important here... Any insight is greatly apreciated!

Seki
  • 11,135
  • 7
  • 46
  • 70

3 Answers3

7

From what the article explains, the script is parsed and executed each time a request is made to the server! This just seems crazy to me!

No, that article is accurate. There are various ways of caching the results of the parsing/compilation, but the script is executed in its entirety each time. No instances of classes or static variables are retained across requests. In essence, each request gets a fresh, never-before execute copy of your application.

I fail to see how I can avoid running the application initialization steps for every request servered!

You can't, nor should you. You need to initialize your app to some blank state for each and every request. You could serialize a bunch of data into $_SESSION which is persisted across requests, but you shouldn't, until you find there is an actual need to do so.

I just really hope that I am missing something important here...

You seem to be worried over nothing. Every PHP site in the world works this way by default, and the vast, vast majority never need to worry about performance problems.

user229044
  • 232,980
  • 40
  • 330
  • 338
  • 2
    I fail to see why I __need__ to initialize my app from a _blank_ state other than the fact that PHP requires this. I suppose I worry over nothing, but it just seems so odd from what I am used to working with (.NET MVC, Sinatra, Rails). –  Jan 06 '13 at 15:21
  • @John - don't confuse languages with frameworks: rails isn't a language, .NET isn't a language, they're both frameworks... PHP is a language, but there are frameworks for PHP as well, such as Symfony, ZF and CodeIgniter – Mark Baker Jan 06 '13 at 15:34
0

No, you are not missing anything. If you need to keep some application state, you must do it using DB, files, Memcache etc.

As this can sound crazy if you're not used to it, it's sometimes good for scaling and other things - you keep your state in some other services, so you can easily run few instances of PHP server.

Marius Balčytis
  • 2,601
  • 20
  • 22
0

A static variable, like any other PHP variable only persists for the life of the script execution and as such does not 'live' anywhere. Persistence between script executions is handled via session handlers.

PassKit
  • 12,231
  • 5
  • 57
  • 75