5 comments about Using XML with Legacy Business Applications.

1. This book provides practical advice and examples on integrating XML into existing business systems. The book is easy to read and follow. The approach of the book is to break the problem down into a chain of simple problems, addressing each as a data 'filter'. The end result is to connect the input/output of a legacy system with the input/output of an XML parser.

   I recommend this book to anyone faced with the problem of using XML to extend the reach of existing applications.




2. Rawlings does a first-rate job of conveying elegant solutions to very arduous problems. If you find yourself in the trenches trying to bridge the technology gap between modern tools and older EDI or flat file based systems - this is your book. Those without the budget for a commercial product will especially appreciate do-it-yourself practical code and easy to follow examples.



3. Mike Rawlin's book deals with the reality that legacy business applications are not readily converted to processing XML-formatted information. While XML works fine as the interchange format, you need to convert between that interchange format and the format your applications understand. Mike covers all of the minor nuances that you need to consider, presents a wealth of knowledge in an easily-understood format, and provides examples to boot.



4. Easy to read, in a refreshing unpretentious style, Rawlins explains numerous complicated concepts associated with using XML. Especially useful are the chapters covering the conversion of EDI formatted data into and out of XML and the converting of one XML format to another XML format. The inclusion of Java and C++ considerations in appropriate chapters provides excellent practical advice.



5. A lot of IT people are busy making different applications running on different platforms "talk" to each other. XML was invented as the "Esperanto" of the IT world to get these systems to understand each other. In practice however it just isn't that simple, as most of these applications don't talk XML yet, until this book.

   This book is a real do itbook. It does not teach you XML or XSLT but shows you how to use it. What I especially liked is that he discusses his design considerations, he wants you to understand the whys. Once he thinks you know the basics he goes back to his basic design and improves it to make it make it fully reusable and modular, making it even beter.

   Mr. Rawlins gives you toolbox of utilities, with the source code, that can become the building blocks for your own application integration system.

   I have not come across a book with as much usable code in my IT career. We have already redesigned quite a few of our systems because of it. If you are into connectivityyou cant be without this book.

   Ps. The word Legacy in the title does not imply big mainframes.

5 comments about Visual Basic 6 Database Programming for Dummies.

1. I've been programming for several years. Did most of my work in MS Access, and Quick Basic before that. Access had spoiled me as far as writing small client/server programs. I was looking for something to introduce me into the world of Database Programming in VB. This book, surprisingly, does a pretty good job.

   I was looking for something to get me started with ADO as well as some of the newer VB technologies, such as WebClasses - a subject I knew nothing about. The book did a fairly good job. It doesn't go in depth into any of the subjects, but gives you enough to wet your appetite, which is what I hoped out of it.

   If you're looking for something to introduce you to the world of database programming using VB, this may be the one you want. Let's face it - compared to other programming books, you can't beat the price.




2. I found this book very useful on my VB projects for school but It could be better. So, if you are new to Database programming this is a good starting point.



3. There was a lot of theory, but not all that much instruction that could be applied outside this book's carefully designed examples. With the increasing popularity, I spend quite a bit of time flipping through it, trying to give it a chance. As a computer instructor, I wouldn't suggest it.



4. Seriously if you want to start building a database in minutes, a good one, this is the book.Got it 2 days ago and am really covering a lot in the book.Very easy to understand and am building my own database right now.Whoever wrote this book I say thanks.



5. The book is great for starting out in DB handling in VB6! It is a bit lacking in an in-depth coverage of relational databases

5 comments about Ajax Hacks: Tips & Tools for Creating Responsive Web Sites (Hacks).

1. Once you have the basics of Ajax down, you might be looking for some ideas of how to apply it to your own applications. Ajax Hacks by Bruce W. Perry fills that particular niche pretty well.
   
   Contents: Ajax Basics; Web Forms; Validation; Power Hacks for Web Developers; Direct Web Remoting (DWR) for Java Jocks; Hack Ajax with the Prototype and Rico Libraries; Work with Ajax and Ruby on Rails; Savor the script.aculo.us JavaScript Library; Options and Efficiencies; Index
   
   Perry collects 80 "hacks" in this volume, which is focused on different techniques for applying Ajax in various ways. The Basics section contains things that you probably will pick up in most Ajax books and tutorials, such as how to check for errors and how to detect which browser is being used. But the dynamic CSS generation ideas were pretty cool. From then on, you get a variety of hacks and code that show you how to do a number of things, such as populating dropdown lists, building mash-ups, and even how to do a drag-and-drop interface without round-tripping to the server with each action. This is one of those books that you probably won't buy with a particular need in mind, but after reading through the material you'll have some ideas that you want to explore further.
   
   Similar to most Hacks titles, it's also not a book you'd buy to learn Ajax. But given the assumption that you know the basics, this book makes a nice addition to your bookshelf for practicality and application purposes...



2. Do you want to add extra interactivity to your web site? If you do, then this book is for you! Author Bruce Perry, has done an outstanding job of writing a book that collects not only dozens of easy-to-grasp, cutting-edge explorations of Ajax technology, such as Google/Yahoo! mapping mash-ups, drag-and-drop bookstores, and single-page web services apps, but a large number of hacks that represent practical advice for Ajax developers.
   
   Perry, begins with a synopsis of the group of well-known technologies that make up Ajax. Then, the author shows how typical it is now to submit form data and to build form widgets such as select lists and checkbox groups using server data fetched in the background with XMLHttpRequest. Next, the author discusses how Ajax applications can cut down on server hits by validating the format of e-mail addresses, credit card numbers, zip codes, and other types of data that users enter into web forms before sending the data. The author then covers a mash-up of Google Maps, Yahoo! Maps, and Yahoo! driving directions, as well as a software interaction involving Yahoo! Maps and a location-to-URL service called GeoURL. The author continues by discussing Ajax as it relates to developers who are immersed in both Java and JavaScript. He also discusses how to use Prototype, a cool open source JavaScript library that includes its own Ajax tools. Next, the author shows you how to get up and running with RoR; and then, moves on to several hacks that illustrate RoR's Ajax tools. Then, he covers script.aculo.us, which is another opensource JavaScript library built on Prototype. Finally, the author provides several tips for real-world Ajax developers.
   
   This most excellent book introduces JavaScript newbies and aficionados alike to useful code libraries, including Prototype, Rico, and script.aculo.us. More importantly, web developers can adapt a number of this book's hacks, some of which are distributed as open source libraries, for their own applications.



3. AJAX Hacks by Bruce Perry is a wonderful companion book for any and all AJAX programmers. AJAX has revolutionized the web programming world, enabling developers to write web pages that act more like real applications that we all know and love. AJAX is a simple technology that allows people to do amazing things, and now there is a book that will show you the ins and outs of creating cool code which is fast, efficient, and easy to use!! With over 400 pages and 80 hacks/tips/tricks, this book is perfect for users that are just learning AJAX and quickly want to accomplish a particular goal. Instead of painfully going through a 600 page book, get to the task you want to accomplish quickly with this excellent book!!
   
   Major topics covered:
   
   01. Ajax Basics
   02. Web Forms
   03. Validation
   04. Power Hacks for Web Developers
   05. Directing Web Remoting
   06. Prototype and Rico Libraries
   07. Ajax with Ruby
   08. script.aculo.us
   09. Options & Efficiencies
   
   Great book, great writing, great deal!!!
   
   ***** HIGHLY RECOMMENDED



4. O'Reilly offers some excellent books. This is not one of them.
   
   Every example I looked at seemed ... not a good example of how to use Javascript. Paging through the book, there are many examples of poor practice in the code. I would be tempted use this book as a source text for bad examples. The ideas might be OK, but the code ... oh please, no.



5. I found the spectrum of AJAX coverage very broad. If you are interested in finding out a little about a lot of areas of AJAX this book is alright. I found it's coverage too broad.

2 comments about FXRuby: Create Lean and Mean GUIs with Ruby (Pragmatic Programmers).

1. GUI programming tends to get ignored when people talk about Ruby. That's a shame, because there are some excellent GUI libraries available for the language. FXRuby has been around for several years and it is probably the most mature. Lyle Johnson, the author of this book, is also the primary maintainer for FXRuby. He is always very helpful in the support mailing lists, and his approachable friendly manner shines through in this book. It's a great introduction, building progressively more complicated applications as you establish a more solid foundation of experience using the library. You'll definitely be ready to use FXRuby in your own apps by the time you're finished with the book, and you'll be hungry to learn more if you're anything like me.
   
   I would have liked to see more about using OpenGL from FXRuby, but it might have made the book unnecessarily cumbersome. It would be nice to see a dedicated library reference someday. Then again, the online RDocs will probably always be the best reference.



2. 'FXRuby: Create Lean and Mean GUIs with Ruby' is a nice introduction to creating GUIs with Ruby. The content is straight and to the point filled with no frills information. Data is spread over 14 chapters and the writing is concise. My only complaints are that I feel this book is too short at just over 200 pages and I wish there was color within. Having said that, I feel this is a good resource for Ruby developers who need to learn how to work with and create GUIs in one of the hottest new technologies to come about in some time (Ruby).
   
   **** RECOMMENDED

5 comments about MySQL and Perl for the Web (Landmark).

1. This isn't a complete review but readers should be aware that this book does NOT cover templates (it doesn't appear in the contents or the index). There's no mention of Template Toolkit or HTML::Template, for example. (Text::Template and HTML::Mason get mentioned as an aside, but that's it) Similarly, there are three chapters on forms, but no mention of CGI::FormBuilder.

   Seems like a big omission to me. YMMV.




2. This is an excellent book. I knew my way around Perl and had done a few relatively simple CGIs before being handed a project to build an application that would allow 50 or 60 employees to enter several thousand customer complaints and email them to the right recipents based on the complaint content. I had a three-week deadline.

   I bought the book and started patching elements of the example applications together until I what I needed almost working. One problem delayed me a couple of days so I emailed DuBois with a question and received a solution within the hour.

   I'd recommend this book to anyone who has a moderate grasp of Perl and Apache. It's one of the most lucid computer books I've ever read.




3. Like many others, I wish I'd seen this book long ago.

   The attention to detail and accuracy of the examples is just incredible!

   This is by far the most used reference book in my library. After repeatedly having to tape the book together, I finally gave it away and bought a new one.

   Following his examples eliminates many potential pitfalls that would otherwise result in hours of troubleshooting.

   I can't imagine how I would have ever learned this information without the expert advice of the author, Paul DuBois. His coverage of CGI.pm is essential as well as his list of other books to read.

   I think I have all his other books as well.

   He even returned email almost immediately!

   My only complaint is that it isn't bound in leather!




4. There are plenty of books about MySQL and PHP in bookstores. Yet, I still prefer Perl as my web page languages, thanks to its powerful regex and the similarity to C grammar (Some functions have exactly the same name and take the same arguments as in C).
   
   For web applications, a backend database is necessary (MySQL). But how to access and operate on these dabatases? Perl comes into scene at this point.
   
   I don't understand why people write so many books on PHP and MySQL, and so few on Perl and MySQL. Up to now, Paul's book is the only one I ever saw to cover both MySQL and Perl's application in web pages.
   
   Paul's method is step by step, and the examples are not trivial ones. And he clearly explained the critical parts of his code. He even wrote some packages which can be used as library.
   
   Before reading his book, I feel curious how the dynamic web pages work. Now, after finishing his book, I can understand how a commercial site such as Amazon works.
   
   Finally, I recommend this book be bought with the other title by Paul - "MySQL". This is the book dedicated to MySQL language. It is a good companion to "MySQL and Perl for the Web".



5. Disclaimer: I was given a copy of this book on the condition that I would write a review of it. That said, what follows is my opinion.
   
   This book provides a good "from the ground up" guide for using Perl to do just about anything you'd want to do on your web site, including run an eCommerce site. You need to know a bit of Perl before you start, but even if you don't the examples start out simple enough that you should be able to pick it up as you go, provided you have some programming background. Should you get stuck, there are plenty of pointers to online resources, as well as an appendix to show you how to set up the software used in this book.
   
   The book starts out with the basics: setting up MySQL and Apache to get at your data via the web, including Perl DBI basics. You then get started by writing a simple to-do list application, and in the process create modules that you will use (and build on) later in the book.
   
   Mod_perl is covered, and then progressively more complex form based applications are presented. Many useful techniques are discussed. Once you're just about tired of all the tedium of form based applications, automated form-handling techniques are introduced that use meta-data about the table structures to automatically generate (and validate) input data. Techniques for session management get a chapter as well, presenting very good information on the pros and cons of different session management techniques (IP, cookie, URL key, etc).
   
   Security and privacy get a very good chapter. Not only are issues presented regarding keeping user's information confidential, but cautions are also presented regarding keeping the server secure. SQL injection attacks are discussed, as are defenses against them. Hint: use MySQL's quote() function.
   
   The book closes with a chapter on writing an eCommerce application. All the techniques used in the book are brought together in one application, and it is shown (very well) how they all relate to each other. While the resulting eCommerce application is extremely simple in regards to what it can do, it effectively shows the reader the power of MySQL and Perl together, and provides an excellent reference when writing applications of one's own.
   
   I am a system administrator, and have done a good chunk of web site design (mostly the technical side) and programming. I've been using Perl since 1996, and MySQL with that since 2000 (used mSQL before that). So, yes, I had quite a bit of Perl and DB experience before I read the book. I say that to say this: I still learned things. There were tips and techniques in there that I hadn't thought of, and will make my job just a bit easier the next time I use Perl to write a MySQL based application. Even if you have some Perl and MySQL experience under your belt, the book will still be useful.

5 comments about System 390 Job Control Language, 4th Edition.

1. This book is the "bible" for all Mainframe programmers/analyst. I've had his original book....OS360 JCL decades ago and it taught me everything I needed to know about JCL. The new version is just as good....probably better!



2. I have used Brown's books since his first 370 edition. Brown explains the often obtuse JCL with clarity not often found in technical books. It is an elegant presentation of the most central tech skill to mainframe systems. His handling of utilities is equally well done.



3. This is the bee's knees.

   MVS Job Control Language explained in easy to understand language.

   There is lot's more than just JCL. There are, for example, explanations of file Data Control Blocks, MVS Utilities, compilers, linkage editors and many more subjects of interest to anyone working on MVS.

   An absolute must if you write JCL. I have it to hand on my desk all the time.




4. I really like this book and I would recommend it to anyone who needs a reference to JCL and to grasp JCL concepts.

   For those not acclimated to the mainframe environment I would recommend reading chapter 21-22 first. They cover ISPF and TSO which is the Mainframe "IDE" in the JCL Context. It is the method in which you code JCL, submit JCL, Debug JCL. I know the focus on the book is JCL, but I would have thought the ISPF TSO Chapters would be in the beginning. Still, a well written book.




5. In days past when I was up to my tush in alligators while attempting to drain the swamp (of IBM mainframe applications) I used only one reference each and every day: this book.
   
   This may be the only book in the world that makes IBM's condition code job control understandable.
   
   With this book you can make IBM's JCL rock and roll to your music.

5 comments about UML Weekend Crash Course.

1. The name "UML Weekend Crash Course" is misleading. I don't think anyone can read and understand it in one weekend, unless of course he is reading about six times faster than me. This book has long and obscure sentences and too much of unnecessary information. The chapter on Object-Oriented principles is written so badly, that I doubt in the authors competence. It mentions two major OO postulates "encapsulation" and "inheritance" but leaves out the third one "polymorphism". But he rumbles on for pages about some unrelated stuff. Also, this book was published before the UML-2 standard came out, so it is somewhat outdated. I would recommend "UML Distilled" by Martin Fowler instead of this book.



2. For the most part, it is a pretty good book. I agree it would be difficult to finish in a weekend. Some annoying mistakes in a few places. For example, on p198-200 the figures are full of mistakes and don't follow along with the text. They are not too hard to correct, but you should not have to do so when you are trying to learn something new. I like this type of format for a book where you pace yourself and then have a review and quiz after a short session. Not too bad, but could be better.



3. The book uses simple and direct language to explain the elements of UML. The examples clearly reveal the key concepts critical for understanding the modeling elements. The book has a perfect level of detail. Unlike other books I have started reading about UML, this book does not go into long commentaries or sidebars about UML, design, and standards. As a result the book allows one to work through the material quickly and will serve as an excellent long-term reference.



4. A number of books have been written about the "Unified Modeling Language" (UML), but few are as easy to understand as the 2002 book "UML Weekend Crash Course" by Thomas A. Pender. Intended to be read over the course of a weekend (beginning on a Friday evening and ending on the following Sunday afternoon), the book is divided into six parts based upon time: Friday evening, Saturday morning, Saturday afternoon, Saturday evening, Sunday morning and Sunday afternoon. Now, just because the author intended that someone would be able to completely read the book over the course of a single weekend doesn't obligate any reader to do that. However, the reader should expect to obtain at least a basic understanding of the fundamental diagrams used in UML: use case diagrams, activity diagrams, class diagrams, object diagrams, sequence diagrams, collaboration diagrams, package diagrams, component diagrams and deployment diagrams. Of these, probably the most important are the use case diagrams, activity diagrams, class diagrams, sequence diagrams and package diagrams.
   
   Though the author points out that UML diagrams can be done by hand, anyone who needs to use UML diagrams should use a software package to simplify their construction and storage because UML diagrams can become rather complex and may require periodic changes, especially when being used to design a new software application. Though there are a number of commercial applications available for UML design, there are also free UML design packages available for download from the Internet, including a few that are used interactively within software IDE's. (The latter may also have auto-code generation.)
   
   As with any software language or modeling tool, it takes time to learn UML. In my opinion, the book "UML Weekend Crash Course" will accelerate that learning process, but you will no doubt require other UML resources (books & software), as well as experience. If you need to learn UML quickly, then I highly recommend this book, which I rate with 5 out of 5 stars. As an experienced software engineer, this book was an invaluable tool for learning UML and continues to be a useful reference.



5. I think the book was good but the title is misleading. The author fails to engage the reader with "lab work" that would truley be needed to be a weekend course. It simply has text and review queestions wich is not enough interaction to keep a person engaged in the material. So what happend to me was that by Saturday morning I wasn't involved enough to continue. Now I just pick up the book during down time at work and read a chapter here and there. I think it is an easy read but I wish I was actually applying the information as I learn it.

5 comments about Sams Teach Yourself Microsoft Visual Basic .NET 2003 in 21 Days (2nd Edition) (Sams Teach Yourself).

1. chapter on OOP is great for beginners.
   most comprehensive vb.net book that i have read.
   ...and this is book #12 in my collection.



2. I have toyed around with Java and PHP and some Visual Basic 6. I knew the craze surrounding VB.NET was strong so I took up this book. One of the best purchases I've made, to be sure. It's simplified so you get your feet wet, and then goes on into more indepth topics. It's a bit lean on the DataView (sorting and filtering, etc) but other than that I applaud this Holzner. Great piece of work.



3. It's a good book, but yes as many have said its got lots of errors. Most computer books have lots of errors.
   
   I wish the book would have a website with the solutions to end of chapter applications and other goodies, but it does not come with anything other than the source code for the book.
   
   Anyway, I use this book for one of my classes: http://iws2.ccccd.edu/bbenavides/ITSE2349_Holzner/Advanced.htm
   
   In the end, I would say its one of the best vb .net books I have read.



4. I teach an introductory programming class in college and will be looking for a more introductory book. Those things that are essential to programming, a class-worth of learning, are taught in ONE DAY of the 21 days. That one day became 1 1/2 month. I also think the order of the days could be better: Simple subjects should come sooner than more complex ones.
   
   Now for you techies here is what I am saying: Control Structures such as if/then, loops, arrays, and such are taught in one chapter. Then functions and subroutines and classes in the next. If this is your speed, go for it!
   
   In short this is for either experienced or enthusiastic programmers. Those programmers could finish a day in one whole 8 hour day. But if you are a beginner don't start here.



5. This book didn't click with me. There were no aha moments. "Let's review how check boxes work; let's look at Radio Buttons." I'm gonna try Francesco Balena's book next.

3 comments about Cics for the Cobol Programmer: An Introductory Course (CICS for the COBOL Programmer).

1. This book, along with Lowe's Part 2: Advanced course, is on my desk at all times. I have been a mainframe programmer for 37 years but altho I have done lots of interactive programming, somehow I never used CICS. I am currently doing lots of Year 2000 changes to CICS systems and these books have made it possible for me to do so. If you want less basic detail, he also has written The CICS Programmer's Desk Reference which is for the programmer with real CICS training. All three of these books are seen on shelves in any IS shop so check 'em out to see which you want



2. I took two years of COBOL, then JCL, and now CICS. Both my JCL and CICS classes used Lowe's books. The layout of these books is bad. The books are just plain ugly. These books are just as text oriented as COBOL itself. The few pictures that are included are hard to understand. In general, almost all of CICS is covered, but it takes time to figure what is being covered. The manufacturing process for these books is bad, too. The books are cut lop-sided, to the point where some of the text is lost. I had no page numbers because they were cut off. A friend of mine had pages where the left side of the page was cut off. BAD QUALITY.



3. I found the book informative and simple. Good for a beginner, which is its objective. I have one complaint and I hope the author and/or the publisher will read this. In many instances with few exceptions the references to the charts, illustrations and examples require turning a page instead of being able to stay on the same page while looking at the graphic. At first this was a minor irritation, but it grew to be a MAJOR FAILING. Help, please in the next edition of this book put the explanation on the same page as or the opposite page from the illustration or example that it describes.

4 comments about M Programming: A Comprehensive Guide.

1. M is a delightful applications language. Recently I've been struggling with C++ STL, trying to use the "map" container to get perhaps a tenth of the functionality you get from an ordinary M variable, and, believe me, I miss M.

   This is the M book we've all been waiting for, and it delivers exactly what it promises. It is, as the blurb says, "the only source M programmers at all levels need."

   The style and presentation reminds me a little of Stoustrup's book on C++: the organization and style are tutorial, but not elementary. It is up-to-date with the current standard.

   What I particularly admire about it, and what is all too rare in computer books (especially those written by professors of computer science) is that it displays an intelligent awareness of real-world commercial implementations of M. Too many books either describe a pure-standards abstraction on the one hand, or a specific vendor extension on the other. Walters identifies popular M implementations by name and calls attention to variations where appropriate. Like M itself, Walters' book is directed at real programmers trying to solve real problems in the real world.

   There are a few places where one can see that the book is an (extensive) rewrite of his older book, rather than a completely new work. I thought it was harder to locate the "argumentless DO" than it should have been, and I felt there should have been a coherent discussion in one place explaining the (historically weird) relations between the various forms of DO, and when $T is and isn't stacked. Similarly, it is disconcerting to see on page 199 that the "NEW" command is described as a "recent extension... not yet formally included in the standard." These are cosmetic problems that do not seriously mar the book I've been waiting for.




2. This book provides the needed instruction for a beginner with no knowledge to learn the fundamentals of M programming. Combine the book with a free M program downloaded from the internet and you are on your way to becomming a beginning programmer.



3. This book does a good job of explaining the reasoning behind the language's (sometimes strange) behavior--most of the time, anyway. The book suffers from numerous typos in the code fragments. Also, it would be nice to have a nice reference section where each command's syntax is explaned succinctly; this is important, especially because M is not a free-form language, i.e., the white spaces are significant.



4. Was trying to write a mumps interpreter. This book ended up being not so useful. Early in the book, he has a completely wrong definition of "bootstrap loader." This bothered me, because mumps is such an old language, you would think someone that knows mumps would know about the meaning of that phrase. In any case, I believe the author knows Mumps completely, but I did not find the book energizing or inspiring.