Secure PHP Development: Building 50 Practical Applications

Features

• Cover Type: Paperback with 840 pages
• Published by: Wiley; Pap/Cdr edition March 15, 2003
• Written in: English
• ISBN 10 Number: 0764549669
• ISBN 13 Number: 978-0764549663
• Book Dimensions: 9.2 x 7.5 x 2 inches
• Weighs: 3.2 pounds

Product Description
* Offers fifty practical and secure PHP applications that readers can immediately put to use
* Explains the entire life cycle of each PHP application, including requirements, design, development, maintenance, and tuning
* Reviews application development line-by-line and module-by-module to help readers understand specific coding practices and requirements
* Applications can be readily adapted to many real-world business situations
* CD-ROM contains fifty ready-to-use PHP applications, an evaluation version of Zend tools, and the latest versions of PHP, Apache, and MySQL

Book Info
Guide for intermediate to advanced level developers, showing how PHP applications can be developed by keeping security considerations in focus. Shows how to take advantage of an object-oriented approach to PHP programming to develop highly maintainable, extensible applications for Web and intranet use. Includes index. Softcover.

Reader Reviews
I normally like to be charitable, but this publication really has nothing to recommend it. Don't touch it with a bargepole. It's a book about secure, object orientated PHP applications by a guy who doesn't understand security, doesn't understand OOP and can't write. Despite the title "Secure PHP", there are whole classes of security exploits which are not even mentioned. There is no comprehensive and authoritative discussion of security at any point. The code samples are poorly laid out, riddled with errors, littered with notes to the author from the technical reviewer, and astonishingly repetitive. You will often get large chunks of code repeated many times just to show changes in a couple of lines buried somewhere in the middle. Not that the code is worth the effort of reading. The design is often naive, the organisation unclear and the coding practices poor. For example, he uses a naming convention for constants ($MY_CONSTANT) rather than defining proper constants as provided for by the PHP language via define(). Another example: on page 41 he exhorts his readers to use good naming standards. Yet the abstract application class that forms the core of the book is full of method names such as: name() number() currency() show_status()... I could go on. There are dozens of other equally cryptic examples. The copy editing and proofreading is the worst I have ever seen in a technical book: it is a disgrace to the profession. There is a grammatical error in the second sentence! Here is a sample of what you can expect, from the 3rd page: "Next, you need to consider how user interfaces will be presented and how can you allow for maximum customization that can be done without changing your core code. This is typically done by introducing external HTML templates for interface." Even the section headings are ungrammatical: "Using relational database" (p21) The 16 editors and proofreaders credited in the frontmatter should hang their heads in shame. This has severly damaged my confidence in Wiley as a brand - they clearly have no concept of quality control. I will be very wary of buying their products in future. The cover strapline "Timely. Practical. Reliable." is a sick joke... Comment | | (Report this)