Categories
php

php|architect agosto

In questo numero di php|architect

An introduction to AJAX and JPSpan
In February, AJAX burst onto the internet leaving hundreds of experimental projects in its wake, talk of web 2.0, and truck loads of hype. Don’t let the hype scare you away, AJAX offers lots of benefits. Let Joshua Eichorn introduce you to AJAX and then get to work building a scrolling table using JPSpan, to get a practical introduction to the new technology.

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-theft is commonplace, and crackers are waiting with itchy palms to make your script accessible to the masses for zilch, author Alasdair Stewart will show you how to keep the doors of script piracy locked, bolted and chained shut, and for less than you might think.

Release Your Next Project as a PEAR 1.4.0 Package
With the release of a stable PEAR 1.4.0 installer on the horizon, now is a good time to get familiar with the new features provided by PEAR 1.4.0 that can make distribution of your open source and proprietary libraries and applications easier than ever before. Returning author Clay Loveless gives you a practical example in this piece.

PHP at Home
Do you have “dumb” appliances at home that you wish were a little smarter? Have you ever wished you could control the lighting in the next room from your terminal? Author Ron Goff has done just this, and all with our favorite language–in this article, he shows you how.

Security Corner
Are you stuck in a shared hosting environment? Perhaps your server hosts many PHP sites, and you wonder about its benefits and limitations? Columnist Chris Shiflett gives you the scoop a long-time PHP feature: safe_mode.

Tips & Tricks
You’ve heard a lot of buzz about security in PHP, lately, but you’re still confused about this “input filtering” thing? Ben Ramsey lends a helping hand in part 2 of his mini-series on this technique.

Other Peoples’ Code
We shouldn’t be writing code anymore. By now everything should already have been written and we should just be stitching together libraries and prewritten components. We should be, but we often don’t. Are we blindly following a “not invented here” philosophy and needlessly reinventing wheels? Or are we right to be nervous? Read on for Marcus Baker’s insight

ciauz