PayPal Hacks is a book about developing software and websites that use PayPal. When deciding on what example code to include, we the authors thought it made sense to write most of the code for one programming platform, the idea being that any programmer could get used to the example code style and learn the concepts more quickly that way. We chose micr*soft Active Server Pages--ASP and ASP.NET--because it is a popular programming platform that does both scripting and SOAP calls well. Our plan worked fairly well, and we've received comments about the book such as "Will Repay Its Cover Price Quickly" and "the writing is [clear], lucid, and concise."
The downside, however, is that programmers who don't write code in ASP are left with examples they can't readily use. So we've received some remarks such as "too micr*soft-centric" and even "Could have been useful, if. . . ." And therein lies the dilemma: Do we write a book that is consistent, where the code leverages code in previous chapters? Do we choose a "platform neutral" language like PHP, even though its SOAP support is lacking? Or do we rotate code examples between multiple languages, thereby losing the ability to build upon previous examples?
http://rapidshare.com/files/106805438/PayPal_Hacks.rar
open 
34 
48 
63
| Average: 