php[architect]

by Jason Lustig

You may already use database abstraction in your applications, perhaps through one of the available data-base abstraction layers, such as PEAR::DB, or PDO (see the PDO article in this issue), but what about various idiosyncrasies in the actual SQL? Perhaps you’ve never even considered this problem. This article will help you the data abstraction beast.

by Chris Cornutt

If you’ve been around the internet for any length of time, chances are you’ve seen a weblog. Chances are, if you’ve seen a weblog, then you’ve seen a trackback. You might not have known it at the time or even understood what it was, but more and more of the blogging tools out there are using them. So, what are these elusive trackbacks and why do they even exist? Author Chris Cornutt explains.

by Oz Solomon

Automated testing can greatly improve the quality of your product. In this article, Oz presents a framework for creating automated tests that can simulate end-user activity. By leveraging the full faculty of Internet Ex-plorer, these tests can do just about anything that your users can do.

by Ilia Alshanetsky

A common complaint of the anti-PHP “expert” is the lack of a bundled, uniform database access component. With the advent of an improved object model, in PHP 5.0, a few of PHP’s core developers decided that the time has come to fill this hole with PHP Data Objects (PDO). The package, itself, has been in PECL for quite a while, now, but with the upcoming release PHP 5.1, PDO will be bundled in the main PHP distribution. What does it do? How does it work? One of PDO’s main developers, Ilia Alshanetsky, explains.

by Chris Shiflett

Peer reviews are one of the most useful and underutilized development techniques. Although professional security audits tend to be quite expensive, peer reviews can offer a great deal of value at a decreased cost. With a moderate understanding of how to audit PHP code, you can be a valuable asset to any PHP development team, and columnist Chris Shiflett shows you how.

by Marcus Baker

Bug-free code is code you can understand completely. Unfortunately, it doesn't take much to cause us uncertainty. Even a small amount of complexity will place demands on our memory, and our memory is extremely limited. If we tax our brains, we will get bugs. Marcus Baker examines how the number of bugs in a piece of code can be correlated to its readability.

by Ben Ramsey

This month’s installment of Tips & Tricks concludes the series on filtering input, providing practical examples and helpful tips to filter input using regular expressions, test for the length of data, and ensure acceptable values.