In a response of sorts to these interview questions posted by Nick Halstead, Matt Wilkin took the next step and worked up the answers for the questions in a new two-part series.

Well at another blog they shared some pre-interview questions from Yahoo for a PHP job. The only problem is they never provided the answers. So that's what I'm going to do now.

Part one answers questions one through eleven and the second part wraps things up with the answers for questions twelve through twenty-two.

In a response of sorts to these interview questions posted by Nick Halstead, Matt Wilkin took the next step and worked up the answers for the questions in a new two-part series.

Well at another blog they shared some pre-interview questions from Yahoo for a PHP job. The only problem is they never provided the answers. So that's what I'm going to do now.

Part one answers questions one through eleven and the second part wraps things up with the answers for questions twelve through twenty-two.

The Jayson Minard continues his "Blueprint for PHP Applications" series on the Zend Developer Zend today in part two, a look at creating and setting up the "bootstrapper" file mentioned previously.

In Part 1 of this article I talked a lot about funneling. Sending every request to one PHP file that then controls the flow of the request into our application code. This one PHP file is called the "Bootstrapper" and deals with everything in common for every request our application receives. The bootstrapper can setup, configure and gift wrap everything that all pages have in common. It can make sure the include path is setup correctly, that the environment is configured correctly, all PHP settings are set, that common model objects are loaded, and that the front controller is invoked to begin your MVC processing.

If you setup the bootstrapper correctly your application code will be more manageable and consistent, along with being easier to write in the first place.

They focus on teh directory structure in this part, demonstrating the correct structure, how to set the .htaccess to coordinate with it, and the creation of a simple PHP file to handle all incoming requests.

The Jayson Minard continues his "Blueprint for PHP Applications" series on the Zend Developer Zend today in part two, a look at creating and setting up the "bootstrapper" file mentioned previously.

In Part 1 of this article I talked a lot about funneling. Sending every request to one PHP file that then controls the flow of the request into our application code. This one PHP file is called the "Bootstrapper" and deals with everything in common for every request our application receives. The bootstrapper can setup, configure and gift wrap everything that all pages have in common. It can make sure the include path is setup correctly, that the environment is configured correctly, all PHP settings are set, that common model objects are loaded, and that the front controller is invoked to begin your MVC processing.

If you setup the bootstrapper correctly your application code will be more manageable and consistent, along with being easier to write in the first place.

They focus on teh directory structure in this part, demonstrating the correct structure, how to set the .htaccess to coordinate with it, and the creation of a simple PHP file to handle all incoming requests.

From the Zend Developer Zone today, there's the continuation of their "Blueprint for PHP Applications" series, this time focusing on bootstrapping (part 1).

The definition (of bootstrapping) from Wikipedia has more flair to it than I can probably give this article, but nonetheless bootstrapping is an incredibly important part of a PHP web application. It is the ignition, the launch-pad, the booster rockets, and even the safety gear for our trip through PHP Best Practices. Without a well designed bootstrap, our application will never get off the ground.

The general idea behind the bootstrapping is forcing all of the requests to a domain to be funneled through a central script and branching out from there. They talk about how to use Rewrite rules to accomplish this and how to set the setup. He finishes the post off by bringing it back to the layout of the application, pointing out where it fits in.

From the Zend Developer Zone today, there's the continuation of their "Blueprint for PHP Applications" series, this time focusing on bootstrapping (part 1).

The definition (of bootstrapping) from Wikipedia has more flair to it than I can probably give this article, but nonetheless bootstrapping is an incredibly important part of a PHP web application. It is the ignition, the launch-pad, the booster rockets, and even the safety gear for our trip through PHP Best Practices. Without a well designed bootstrap, our application will never get off the ground.

The general idea behind the bootstrapping is forcing all of the requests to a domain to be funneled through a central script and branching out from there. They talk about how to use Rewrite rules to accomplish this and how to set the setup. He finishes the post off by bringing it back to the layout of the application, pointing out where it fits in.

For those of you that have been following along, PHPBuilder.com has posted the third and final part of their "Using XML: A PHP Developer's Primer" series. Even if you haven't been keeping up, it's worth a look.

In this edition, they look at more advanced topics - a deeper look at Ajax and how to style the data you get back with XSL, both on the client and sever.

To start, they look at XSL - what it is, how it's used, and some code examples of both the XML and XSL structures to style XML data into a valid HTML page. Of course, you'll need the PHP extension to get this all working, so they step you through the installation/enabling of that as well.

They touch on other topics (like passing variables to a stylehseet and XSLT in Javascript) before getting to a simple XSLT and Ajax example - pulling book data and formating it with examples of both the PHP and Javascript sides.

For those of you that have been following along, PHPBuilder.com has posted the third and final part of their "Using XML: A PHP Developer's Primer" series. Even if you haven't been keeping up, it's worth a look.

In this edition, they look at more advanced topics - a deeper look at Ajax and how to style the data you get back with XSL, both on the client and sever.

To start, they look at XSL - what it is, how it's used, and some code examples of both the XML and XSL structures to style XML data into a valid HTML page. Of course, you'll need the PHP extension to get this all working, so they step you through the installation/enabling of that as well.

They touch on other topics (like passing variables to a stylehseet and XSLT in Javascript) before getting to a simple XSLT and Ajax example - pulling book data and formating it with examples of both the PHP and Javascript sides.

Justin Silverton continues his "PHP Security Mistakes" series with this new post, looking at issues surrounding system calls, file uploads, and including files into your scripts.

In one of my previous articles, I mentioned the top 5 security mistakes made in PHP. This article is a follow-up, with some more common security mistakes.

For the three topics he describes the functionality PHP offers for them as well as a suggestion or two as to how you can prevent these issues from showing up in your scripts.

Justin Silverton continues his "PHP Security Mistakes" series with this new post, looking at issues surrounding system calls, file uploads, and including files into your scripts.

In one of my previous articles, I mentioned the top 5 security mistakes made in PHP. This article is a follow-up, with some more common security mistakes.

For the three topics he describes the functionality PHP offers for them as well as a suggestion or two as to how you can prevent these issues from showing up in your scripts.