We're going to take these concepts [from the previous article] further and add a new one: REST. In the course of this series so far, we've only been discussing how to use the Router to examine and act on different parts of a URL.

He gives a list of possible headers that could come from a client (like Accept-Charset or Content-Type) and how these can be directly pulled in to the CakePHP routing system. A few extra bits of code later and your app can be mapping requests directly to the controllers for the actions the user's requesting. All that's left is to serialize the results back into XML to echo out.

Here are some resources to help you not only learn PHP, but also reference PHP information should you ever need it. This list isn't exhaustive, however, it should provide you with a lot of help when you need your PHP fix.

Some of the sites included in their list include:

• W3Schools PHP Tutorials
• Good PHP Tutorials
• PHPFreaks
• ONLamp

Developing in PHP isn't a textbook science. There's skill to it, and that skill comes from experience. Now, you could try your hand at every single PHP development challenge out there, or you could learn from the experiences of others, widely published on the web in blogs and developer portals.

Included in the list are sites like php|architect's C7Y site, Planet PHP and the the Zend Developer Zone (oh yeah, PHPDeveloper.org made the list too!)

Before jumping into the development of a Zend Framework coding standard for the PHP_CodeSniffer Pear package, I spent some time revisiting and compiling the available Zend Framework coding standards into a handy one-paged Pdf document.

You can download the file here or, if you want something a bit more "spread out", check out the coding standards on the Zend Framework website.