CGI Programming with Perl (Paperback)

by Gunther Birznieks (Author), Scott Guelich (Author), Shishir Gundavaram (Author)

Editorial Reviews

Amazon.com Review
The appearance of the second edition of CGI Programming with Perl heralds the beginning of the neoclassical era of Web service. CGI--or common gateway interface--is the original back end for client-driven, dynamic Web-page service and deserves consideration as the Romulus of the Internet Empire. But, where first-edition author Gundavaram described the lonely Romulus laying the brick foundation of dynamic Web-page service in 1996, second-edition collaborators Guelich and Birznieks have pitched in to resurrect Romulus amid the crowded streets of modern Rome. Why bother? Surely four years have brought technological revolutions (Java, PHP, ASP, ColdFusion) that render CGI's original brick-by-brick approach as obsolete as, say, Roman mythology--or bricks and mortar.

And yet not. It is an ambiguous blessing that the original CGI persists, adhering to the underside of Web service by the duct tape that is Perl. This point is not missed by Guelich, Gundavaram, and Birznieks, whose advocacy of CGI is both bolstered by the growing applications module base of Perl and tempered by their awareness of CGI's structural limitations. Both new and returning readers of CGI Programming with Perl should browse the last chapter first in order to appreciate the proposed solutions to CGI's greatest sin: its impractical slowness in a world of a million-hits-per-day Web service. The chapter describes CGI-compatible FastCGI and mod_perl technologies that circumvent the process-spawning slowness of the simple CGI. Advanced users might want to skip directly to O'Reilly's fine mod_perl tome, Writing Apache Modules with Perl and C, by Lincoln Stein and Doug MacEachern.

The authors' second pass at CGI pedagogy is a lucid, honest, and expanded account that develops functionality of dynamic Web pages in a rational progression--from HTML client-server and CGI syntax basics to general input/output, forms, e-mail, graphics, and simple database applications, including maintaining client state and data persistence under the otherwise stateless HTTP protocol. The authors offer synopses of cookies, JavaScripting, server security, and XML, all of which are described in detail in other books.

Whether or not neoclassical CGI is fast enough for your purposes--perhaps for guarded intranets--bear in mind that CGI is the standard to which every other Web server has had to respond. The second edition of CGI Programming with Perl is still the best introduction to the classics. --Peter Leopold

Product Description
The Common Gateway Interface (CGI) is one of the most powerful methods of providing dynamic content on the Web. CGI is a generic interface for calling external programs to crunch numbers, query databases, generate customized graphics, or perform any other server-side task. CGI programs can be written in any programming language, but Perl is by far the most popular language for CGI. CGI programmers appreciate Perl's text manipulation features and its CGI.pm module, which gives an well-integrated object-oriented interface to practically all CGI-related tasks. Based on the best-selling CGI Programming on the World Wide Web, this edition has been completely rewritten to demonstrate current techniques available with the CGI.pm module and the latest versions of Perl. Topics include incorporating JavaScript for form validation, controlling browser caching, making CGI scripts secure in Perl, working with databases, creating simple search engines, maintaining state between multiple sessions, generating graphics dynamically, and improving performance of CGI scripts.

See all Editorial Reviews

Product Details

• Paperback: 451 pages
• Publisher: O'Reilly Media, Inc.; 2 edition (January 15, 2000)
• Language: English
• ISBN-10: 1565924193
• ISBN-13: 978-1565924192
• Product Dimensions: 9.3 x 7 x 1.3 inches
• Shipping Weight: 1.5 pounds (View shipping rates and policies)
• Average Customer Review: 3.4 out of 5 stars See all reviews (33 customer reviews)
• Amazon.com Sales Rank: #361,133 in Books (See Bestsellers in Books)

  Popular in this category: (What's this?)

  #4 in

  Books > Computers & Internet > Programming > Languages & Tools > CGI Programming

Customer Reviews

Most Helpful Customer Reviews

29 of 29 people found the following review helpful:

4.0 out of 5 stars What's different about this book?, November 19, 2001

By	"sherzodr" (East Lansing, MI USA) - See all my reviews

While there're a few boooks available on CGI/Perl, what's different in this book you'd ask. If we compare it with "CGI Programming 101" by Jaqueline, it's more advanced and excersices better programming style. Uses 'strict' pragma and -wT switches ALL THE TIME, which I liked a lot. The programs are also compatible in mod_perl enviroment, which prove the fluency of the authors in Perl and Web Programming. Unfortunately their those capabilities don't make them good writers. They don't spend enough time on some of the concepts they introduce. They sepend more time and space then requried on JavaScript(chapter 7), which is about 23 pages, and spend only 16 pages on Data Persistence (chapter 10). But in Data Persistence chapter they tried to cover Text files, all kinds of file lockings, temporary files, DB_File, MLDBM, SQL, DBI. Now you have a rough picture of how dEtAiLeD their topisc are. Here I'll try go over chapters with comments and will be suggesting alternatives for the topic wherever it's applicable

Chapter 1, 2 and 3 give some history of the WWW and CGI. Also provide a smaple CGI application for getting started. I think chapter 2, "Hypertext Transfer Protocol" was pretty informative, and I ejoyed it a lot.

Chapter 4, "Forms and CGI" go over some form anatomy and elementary ways of encoding and decoding form input, which you might find usefull.

Chapter 5 is entirely dedicated to CGI.pm and it's application. I still think CGI.pm's documentation available online (or with your Perl distribution) does way better job than this one chapter.

Chapter 6, "HTML Templates" gives some nice examples of HTML::Template and Embperl usage. They spend good space on these, but only about 3 pages to cover Mason. Of course, the chapter can't take you too far without the original documentations of those mentioned libraries which are available online.

Chapter 7, as I mentioned was dedicated to JavaScript and JS validation. I think they were not supposed to spend so much time on JavaScript. For this one, go get JavaScript Bible, 4th edition by Danny Goodman.

Chapter 8, Security covers the security guidelines already available online as W3C's security FAQ by L. Stein and John Stewart.

Chapter 9, "Sending Email" was probably my favorite. It covers 'sendmai', mailx and mail and procmail. Spends good 18 pages on the topic and shows an examile that uses Mail::Mailer

Chapter 11, Maintaining State, was really poor. There's nothing much to learn in that chapter. For more profesional session management examples, I suggest you "MySQL and Perl for the Web" by Paul DeBois and Apache::Session manual available online.

Chapter 12, "Searching the web" give some advanced examples of web searching. The example of Inverted Index Search using DB_File was my favorite.

Chapter 13, "Creating Graphics on the fly" give some examples of dynamic graphic generation using GD, Image::Magick and GD::Graph. I could give this chapter hmmm... 3 stars :)

Chapter 14, "Middleware and XML" was the one I just skipped over.

The last 3 chapters of the book are dedicated to debugging, coding with style and eficiency with mod_perl and FastCGI.
For debugging and style, I recommend "Programming perl 3rd edition".

Overall, i benefitted from the book a lot as it implies from my review. But still wanna save my 5 stars for the 3rd edition :)

28 of 31 people found the following review helpful:

1.0 out of 5 stars Rush job and it shows, July 25, 2000

By	"jb4mt" (Kearney, NE) - See all my reviews

This book is full of typos, which is forgivable if the code examples don't have typos, but they do. For instance, in the code for upload.cgi on pg 99, the following declaration is made:

use constant UPLOAD_DIR => "/usr/local/apache/data/uploads";

Note this does NOT end with a slash. Later, though, a loop is initialized as follows:

until (sysopen OUTPUT, UPLOAD_DIR . $filename, O_CREAT | O_EXCL)

$filename is taken from user form input, but unless the user was omniscient and put a slash at the beginning of the name he assigned, then the expression "UPLOAD_DIR" . $filename would evaluate to something like:

/usr/local/apache/data/uploadsbleedin_file_name

instead of the correct: ".../uploads/bleedin_file_name". Oh, and speaking of putting a slash at the beginning of the file name....there is code that is supposed to prevent such, as evidenced by the line:

error($q, "Invalid file name; files must start with a letter or number.");

I don't know about slashes, but it didn't prevent me from sending a file name through that begin with a tilde.

Yes the book covers some things you won't find anywhere else, but a lot of the stuff it covers is better covered elsewhere: OReilly's "Webmaster in a NutShell" has better coverage of HTTP. It (Webmaster) also discusses using the use statement to reference a library in a path where you might have had to manually install it in your virtual hosting directory if for instance you couldn't convince your ISP to upgrade to the latest version of CGI.pm. This wasn't covered in the CGI book, which is supposed to be solely about CGI, whereas the Webmaster book not only covers CGI/Perl, but also JavaScript, PHP, etc.

Don't waste your money....I'm sorry I did

21 of 23 people found the following review helpful:

3.0 out of 5 stars NOT a "quick and dirty" CGI reference..., August 21, 2000

By	H. Lanza (Austin, Texas USA) - See all my reviews (REAL NAME)

You must be careful when usign this book. I found myself wasting a lot of time typing (oreilly's ftp site was down, and has been down lately--what can I say?) and implementing the examples in the book only to get to the end of the chapters to find out that the authors were holding out on me for a better solution. For example: Parsing forms? Don't implement anything on Chapter 4, "Decoding Form Input." Wait until the next chapter about CGI.pm. Searching the web server (Chapter 12)? Wait until the end of the chapter before implementing anything, or waste alot of time.

Don't get me wrong, this book has some decent information in it. And there is much learning to be done in reviewing how NOT to do certain things. However, I'm not sure how many people read CGI books from cover to cover.

Bottom line: the authors should have been more mindful of their audience's time constraints and should have tailored the exposition of material accordingly.