php and the "white page of death" - would it apply to API too? -


I have done a little PHP and I had a fair share of "white pages of death".

Some friends are working on a server API they want to implement with PHP. API concepts are independent modules but they will be deployed on the physical server running the same API instance.

So my question: will these modules really be independent? Will "white pages of death" probably not apply to the API? They say that they will be independent classes for each module, but my guess is that they all will run in the same php memory space - so if there is a serious flaw in a module (one of the worst cases is the white page of the trigger trigger) , Then it affects all the other modules, as well as bring them down effectively?

If I present this question as a less experienced php boy, and if more information will be needed properly the answer to this question.

AFAIK They also do not use a framework, it's all handish.

There is no "single php memory place" in each HTTP request and to operate it inside The PHP code running is completely independent of each other.

One or more bugs in your API scripts, e.g. A syntax error that generates a fatal analysis error on startup will destroy all of your requests using those scripts, but not to reaching memory and negligible there. When a new request arrives in , they will be stopped and prevented from starting in the first place.

Comments

Popular posts from this blog

php - PDO bindParam() fatal error -

logging - How can I log both the Request.InputStream and Response.OutputStream traffic in my ASP.NET MVC3 Application for specific Actions? -

java - Why my included JSP file won't get processed correctly? -