PHP7 Resource Recap

[TomB]

@s_molinari

Which basically means, you can do different things at different times, instead of doing it all with each request. As Stefan points out in the video above, with Appserver, you don’t have to run any bootstrapping scripts with each request. You can store such things (and many others) as a servlet, which start running at server startup and stays in memory until the server is stopped or restarted. It is sort of akin to the Tomcat web server for Java, from what I can tell.

I’ve just put a post up in showcase with my implementation Take a look at the code, it’s surprisingly simple!

A PHP Application server implementation

A few weeks back, @Michael_Morris posted a topic where he suggested that creating/destroying objects on each HTTP request was wasteful. I posted a way of getting around that in the thread, I’ve built on that a little and come up with what I think is quite a nice implementation http://www.sitepoint.com/community/t/a-crazy-idea-mark-script-ready/117312 The basic thought process behind this is that: When you connect to the webserver all that does is run a very minimal script, it doesn’t create …