May I see Your License Please?

Last year, the Business Software Alliance reported that 35%of all software installed was pirated. In a world where code-theftis commonplace, and crackers are waiting with itchy palms to makeyour script accessible to the masses for zilch, author AlasdairStewart will show you how to keep the doors of script piracylocked, bolted and chained shut, and for less than you mightthink.—by Alasdair Stewart

An introduction to AJAX and JPSpan

In February, AJAX burst onto the internet leaving hundreds ofexperimental projects in its wake, talk of web 2.0, and truck loadsof hype. Don’t let the hype scare you away, AJAX offers lotsof benefits. Let Joshua Eichorn introduce you to AJAX and then getto work building a scrolling table using JPSpan, to get a practicalintroduction to the new technology.—by Joshua Eichorn

Release Your Next Project as a PEAR 1.4.0 Package

With the release of a stable PEAR 1.4.0 installer on thehorizon, now is a good time to get familiar with the new featuresprovided by PEAR 1.4.0 that can make distribution of your opensource and proprietary libraries and applications easier than everbefore. Returning author Clay Loveless gives you a practicalexample in this piece.—by Clay Loveless

PHP at Home

Do you have “dumb” appliances at home that you wish were alittle smarter? Have you ever wished you could control the lightingin the next room from your terminal? Author Ron Goff has done justthis, and all with our favorite language–in this article, he showsyou how.—by Ron Goff

Security Corner

Are you stuck in a shared hosting environment? Perhaps yourserver hosts many PHP sites, and you wonder about its benefits andlimitations? Columnist Chris Shiflett gives you the scoop along-time PHP feature: safe_mode.—by Chris Shiflett

Tips & Tricks

You’ve heard a lot of buzz about security in PHP, lately, butyou’re still confused about this “input filtering” thing? BenRamsey lends a helping hand in part 2 of his mini-series on thistechnique.—by Ben Ramsey

Other Peoples' Code

We shouldn’t be writing code anymore. By now everythingshould already have been written and we should just be stitchingtogether libraries and prewritten components. We should be, but weoften don’t. Are we blindly following a “not inventedhere” philosophy and needlessly reinventing wheels? Or are weright to be nervous? Read on for Marcus Baker’s insight.—by Marcus Baker