Software Books

Very good collection of Stellent Content Server. Only reason i gave 4 star instead of 5 is that sometimes it is hard to find stuff you are looking for. I have this book for about 18 months now and i have used it so many times both during new development as well as fixing some bugs.

Now that Stellent is bought by Oracle and not knowing how oracle will integrate Stellent CMS with other oracle products, I would suggest hold off buying it, if you are looking for a long term value. If you looking for only short term use, go ahead and buy it.

brian did a great job of getting right to the matter at hand with excellent real world examples.

I only wish this book was written two years ago. However, it is a very well written book with a good layout and great examples. At last many questions that I did not know to ask have now been answered.

Way to go Brain!

Well written, easy to understand and use, congratulations on a truly useful tool. I have worked with Stellent for many years, and have this book next to my keyboard at all times! Bex has always provided clear answers for the user group, but this provides a clear direction no matter what you need to do with your Stellent system.

Kudos!

If you do any customization to a Stellent Content Server or want a detailed over-view of what can be done to a Content Server, then this book is for you. Both developers and managers could benefit from this book. It's easy to explain what needs to be done or what you are asking for, once you know what can be done within the Content Server.

Finding information is easy in the book and Bex's example are clear cut and to the point.

I found this an exellent book. The original design patterns book drew its examples from C++ applications. I could see a use for the patterns in C++, but I thought most of them would not have been necessary if the code had been written in Smalltalk.

This book did an excellent job of showing how and where the patterns could be used in Smalltalk applications. The authors also extended and clarified many of the pattern so that they were simplier to understand. The book is more than a companion to the GOF book; it is an enhancement of it.

This book gives you a better understanding of the patterns than in its original version (the GoF one). I am not a SmallTalk programmer but a 9 years C++ one. At work I had to use the GoF book and never liked reading it. In contrast to this, the SmallTalk companion is easy to read and you can understand the patterns within the first few lines of their description. Take the Bridge pattern and compare their discussions in the two books. If you really like the Gof one then buy it. But according to me, it would be a big mistake buying the GoF in favour of the SmallTalk companion. Trust a C++ programmer :-)

This isn't a Smalltalk translation of "Design Patterns." Instead, it's a companion to that book. You'll need to read the first one to get the most out of this one. If you have read the first one, you'll find this one is better written and really casts essential light on some of the GOF material. The Smalltalk aspects of this book are really a non-issue (except perhaps showing static-typers how many hoops you don't have to use in Smalltalk). This is required patterns reading.

I bought this book because of the unresolved questions I had after spending so many hours exploring the GoF original book. I am an experience C, C++, and Objective C programmer, not a Smalltalk guru at all. And I found the GoF very confusing and intimidating. My current projects these days are written in Java (I miss Objective C). I looked for a book that would cover the pattern catalog in Java because I was really questioning the purpose of some of them in that language. Creating some mechanism to overcome the C++ language is somewhat understandable, but why bother with Java. Take the prototype pattern for example: "...It's (the prototype pattern) less important (to use it) in languages like Smalltalk or Objective C that provides what amounts to a prototype..." (page 121) Sure, ok, but what about Java? Can you give me an example on how it would benefit a language that doesn't really require it like Obj C, or even Smalltalk? Then the sample code refers to the maze example but not much material is given here. I bought several books with Java and Design Patterns in the title but was very disappointed with the beginner level these books approach this problem. The titles are seductive but the content is not that great. I don't need another ADOO (I've read Larman's book already. Get it if you are new to OO BTW.) So I ended up getting that book as a last resort. And you know what? It's great. I program in Java all day (and sometimes all night, sigh...) and this book spends more time on my desk than the GoF original one. So, if this comments remind you some of your experience, you should give this book a try. And this book lighted up another bulb in my brain: I ended up downloading Squeak and prototyping in Smalltalk some of my projects just for the fun of it, but that's a side effect I guess ;-)

I found this an exellent book. The original design patterns book drew its examples from C++ applications. I could see a use for the patterns in C++, but I thought most of them would not have been necessary if the code had been written in Smalltalk.

This book did an excellent job of showing how and where the patterns could be used in Smalltalk applications. The authors also extended and clarified many of the pattern so that they were simplier to understand. The book is more than a companion to the GOF book; it is an enhancement of it.

Mary Kirtland has written a terrific resource for those who wish to know more (i.e. go from basic to advanced) on how to program with COM and MTS. I found the example code (and companion CD-ROM) very useful and relatively bug free. Some of the chapters include:

Windows DNA (now .NET)

COM (101)

Data Access Fundamentals

MTS

ASP

Extending MTS

Application Definition and Modeling

Building Data/Business Objects

Packaging

Building the Presentation Layer

Debugging and Troubleshooting (an excellent chapter on a tricky subject)

Performance Validation

Deploying

Extending the Application

COM+ (pretty good for when this was written, it is time to update the book with the latest and greatest, however).

Most of the information here is still relevant, especially to those with a smattering of COM or MTS under their belt and are hungry for more. Everything is wrapped up well with a comprehensive index. Well worth the purchase price. Definitely a must along with "Programming Distributed Apps with MS COM+ and MS VB."

This book does a good job of explaining the COM standard from the ground up. The first third is devoted to COM. The rest of the book is an overview of building an enterprise application from the ground up using Microsoft technologies.

I used this book as my primary reference in preparing for the new Analyzing Requirements exam (70-100) in the new MCSD track based on the recommendation of someone I know that passed the beta. It may not be listed as a study guide for the test, but it is far better than the Syngress or Sybex study guide for that test. (They were both fairly useless.)

This is an excellent overview of Microsoft's DNA and the technologies that make up DNA. The pieces of the DNA puzzle are clearly defined individually and the way they relate to the others. The Island Hopper application sample (maintained up-to-date on MSDN) is a great hands-on intro to the topic. The amount of coverage on topics like COM, MTS, MSMQ, etc. is just right: technically deep enough to help you understand the concepts, short enough to prevent you from shifting your focus from the architecture to technologies contributing to the architecture.

You may try to surf Microsoft's DNA pages to understand the topic (and potentially get lost in the amount of links that span hundreds of different Microsoft technologies) or get this "one" book to really understand what Mr. Gates is talking about for the last couple of years.

After being confused by multiple books on Windows DNA I was very happy to see a book that actually showed and an entire application which utilized this technology. Part I of the book offers a very concise explanation of MTS and COM without getting too deep into the subjects. Part II showed examples of components that the sample project utilized. I enjoyed the fact that the author used both VB and VC++ in her examples. Beyond the examples, the author also offered very good insight into component design and tool selection. It was enough to get you up to speed so that you can look into deeper books on the subject.

Everyone always draws the same n-tier diagram and says they are going to build a scalable, MAINTANABLE solution.

This book actually provides a blueprint, not the 30,000 ft view.

At my job, we call it "The Good Book"

It describe all aspects about digital crimes using a clear language. It's very good for neubies.

If you are new to this world this is where you should begin. Digital Evidence contains all the knowledge one could amass by obtaining PHD in computing. Especially when you don't have time for a Diploma. I have bought 5 books pertain to digital crime from USA and UK. But this is the one and only book I am recommending to any one in any continent who want to learn or new to this arena. All the other books in this field for Attorneys or with similar requirements are some what academic and may be boring. The CD-ROM accompanying the book gives you much needed hands on training, otherwise which will cost you at least US $ 4000, if you are to go to a training centre to do the same.

Sometimes, defense attorneys have it easy: one slip-up by the prosecution and evidence is thrown out. Knowing that, law enforcement goes to great lengths to ensure that evidence is appropriately collected and protected. That works well in the physical world, where law enforcement has many generations' worth of experience. But in the modern world of computers and digital networks, where the simple act of rebooting a computer is enough to wipe out large amounts of evidence, law enforcement clearly needs thorough guidance.

Such a resource is here: Digital Evidence and Computer Crime, an excellent book that details the elements of digital crime. Author Eoghan Casey does a superb job of applying forensic science to computers. The information presented here is critical to a diverse audience: law enforcement, attorneys, forensic scientists, and systems administrators, for instance.

While cybercrime law is in some ways similar to other aspects of criminal law, it nonetheless has its own language and categories. For instance, jurisdiction is a key element in both the physical and digital realms, but it is a much trickier concept in the latter. Casey develops this topic and many more. Those new to computers and networks need not worry: the book begins with an explanation of how they function. With the basics out of the way, Casey details how computers can be used in crime and how the evidence created from these activities can be used for later analysis....The accompanying CD-ROM contains simulated cases that integrate many of the topics covered in the text. In all, the book and CD are an excellent introduction to an increasingly important area of law enforcement.

This is an excellent book from a real expert.

Everyone and their brother are writing books about computer security and digital forensics.

The difference here is that Eoghan Casey knows what he is talking about.

Excellent book!

This text was used for the digital evidence and computer crime class that I just completed. The book is clear and easy to understand. It goes into detail only when needed. I was concerned that this information would quickly become out of date, but the ideas presented are current and provide a solid background for understanding any newer technologies that come down the road. I usually sell my books after the semester ends, but I have decided to keep this one.

This is much better than the Oracle Documentation. Easier to read and presents the information in a clear and concise manner. If you can't take the Oracle Security class from Oracle Education this is the next best thing. The only thing bad that I could say about this is . . . . Pete Finnigan could of been brought in to get a different perspective.

Buy this book if you haven't already... it's wonderful!

An easy/enjoyable read full of everything you need to know about locking down a 10gDB install!

Effective Oracle Database 10g Security by Design is sooo helpful.

There is a lot of good info in the Oracle documentation, but David Knox fill in a lot of the blanks.

I'm trying to set up proxy authentication and the book made a lot of assumptions about what I know. The author uses the SCOTT, BLAKE and APP_USER accounts and assumes that we know exactly how these accounts where set up. It would seem that the APP_USER account seems to be the schema owner, or is it the SCOTT and BLAKE accounts. Am I to assume that the SCOTT account is the defualt demo account that is setup by oracle? Being new to high level Oracle security I would have preferred a step-by-step approach to solving my security problems. I noticed that all other reviews where by people that seem to have a handle on this and just needed hints. Even the setting up of an LDAP sever was confusing, we never got it to work and even after following the steps did not get the same things that the author got. Even though I have not been a DBA for too long I have been using Oracle for 20 years now, so I'm not a novice.

It would be easy to be secure if all the data were in one room, there were no connections to the outside world (well I guess you have to have power coming in, but that's all), and there were no people who knew the data.

Unfortunately that's not the real world. Breaking the German and Japanese codes during World War II would have been meaningless if that information wasn't used to sink the submarines, divert the convoy, or be ready at Midway.

The situation hasn't changed, but the integral capabilities of the Oracle database itself have. As security has gotten ever more important, the steps you need to take get every more complex. At the same time, the users of your data can't be expected to agree, they have a job to do and if security systems prevent them from doing their job they will find ways to bypass or ignore the security system.

This book can be read on two levels. First it is an excellent primer on security in general. Second it is Oracle centric so that anyone responsible for security on an Oracle based system need go no further.

Note that the Foreward is by David Carey, former Executive Director of the Central Intelligence Agency. It is generally believed that a big contract from the CIA was Oracle's first major success. The implication is that the CIA worked with Oracle to develop the security system discussed here. If the CIA says it's good enough....

I found it best technical book till date but you should know Flex & Ruby before you can jump into this..

This is a great book. Peter is the #1 expert in Flex + Rails.

The author goes into great detail on how to efficiently get Rails and Flex working together. The book is updated for the latest version of Rails as well as the upcoming Flex 3 release. I've found the book easy to follow along with and enjoy the author's humor spread throughout the book.

As a developer I'm often tasked with making "things talk to each other". Typically if I can I'll use a tool like Flex Builder for a project and if I have a choice I'll pick Java, .NET or Ruby for the server back end - whatever is the best fit. This book only backed up my belief that Rails and Flex really do work very well together. I've learned a lot going through the code both on Rails and Flex.

I also liked how the author is continually refactoring the application (called "Pomodo"), that is where your learning kicks into overdrive. He uses the Cairngorm framework and even RubyAMF. I didn't have any experience in either up until this point. Now I can say I do and it all fits together nicely.

I have used Flex for about a year and I have only dabbled in Ruby/Rails development. I have been curious how I might back a Flex front end with a simple service layer that isn't hard to create, maintain or host. So far I have only worked with Java/Spring/Hibernate backend services which can take a little while to build and integrate (Grails is MUCH faster).

After about 100 pages I'm in interation 4 building an interesting RIA with a Rails backend that I can host on relatively inexpensive server if I wanted to. My only struggles thus far was getting MySQL going properly. But that was only because I forgot a step in installing it.

If you have little exposure to Rails and/or Flex and you feel at home on the command line as well as you do in an IDE like Eclipse, this is a great "project" book for you. I'd say you probably want a primer in Ruby, Rails and Flex before you get going but it is pretty easy follow and has a lot of free professional advice from someone that has obviously been around the block a few times. Peter is very upfront about some things that he has done in the book that should not be considered "best practice".

I am hoping to get some good insight how I might do something similar for Flex and Grails. Regardless, I am confident this is going to be a fun journey!

I wasn't sure whether a mixed-technologies book would be adequate for both reading and reference, especially with two technologies. As both a software engineer and a moonlighting instructor this book was an easy read from the start. Mr. Armstrong explores both Flex 3 and Rails 2 with enough background information on both technologies to get a reader ready to code--and that was just Chapter...err...Iteration 1. The second iteration begins with coding (Hello World) and it doesn't stop. This is a must for your coding library and makes a great textbook for students who enrolled in courses geared toward building web and Rich Internet Applications.

If you read the first book this is an excellent followup to help you increase you understanding of how to build a robot of your own. If you did not a good place is start with the first book Robert Building for Begginers. These books help get you in the thought process needed to build decent robots wather small or big.

The only thing I can say is I bought it for my 16 year old grandson and he said it is awesome.

This review is by my ten year old Robot fanatic:

This book introduces the most common parts (in a beginner type robot) step by step by defining them properly. So far I have made a line following robot almost from scratch. This book sets you up with many different options. It starts with safety and where to obtain parts then moving on to introducing parts. After that you are shown how to setup a solder-less breadboard.

This book (and it's prequel, Robot Building for Beginners by the same author) is extraordinarily good. It picks up where the previous book (which is the best book in existence for the beginning roboticist, in my opinion) leaves off, getting into details of milling parts, microcontroller circuits, and such. A truly wonderful book. If you read the previous book, and then read this book, you will have an excellent grounding in robotics, and have a very entertaining time doing it. Highly recommended!

I am a novice robot builder. I appreciate the thoroughness and practical approach of this book. I have understood and implemented several circuit ideas from this excellent book.

Books like this are refreshingly down-to-earth after reading the usual college text books.

This book can get you started just in the way you would like to. Mike understands what PB developers need to get started with Web development and Jaguar. Although EAS versions have changed, but the basic concepts suc as "stateless/stateful, instance pooling, transaction support, connection, etc" remain the same. This book is not for Java with EAServer - this is PowerBuilder with EAServer - as the name suggests.

This book was written for PowerBuilder 7 (now 7.03) and Jaguar CTS 3.0 (now Sybase Enterprise Application Server 3.6.1.08). While PowerBuilder hasn't changed much EAS most *certainly* has. When Jaguar 3.0 came out there was no database persistence standard for the Java platform, EJB was barely a spec (v 0.4), and a lot of things that we take very much for granted in the J2EE Specification simply didn't exist. Also, Jaguar 3.0 was a much 'clunkier' system to administer than that newer 3.6.1 release that Sybase has done. While many of the concepts discussed in this book from the PowerBuilder side are still applicable, some of the screen shots and processes are dated on the Jaguar side. Still, the book represents a good history lesson if nothing else. Being that this is the *only* book on the subject of using PowerBuilder as a front end to your Jaguar/EAS server-side code I'd say get it. But it's quickly become in *dire* need of a revamp. Are you listening, Mr. Barlotta??

The site was going to use PB7 and Jaguar - exciting! I ordered the book, read it, used the many fantastic code bits to get an n-tier PB7 app up and running. Fantastic book.

4 months later, the client decided to use Java, scrap PB development and sacked me without even a day's notice. Oh well. I still think Jaguar and the book and PB7 are tops! But the lesson learned is that Powerbuilder is on the way down and out!

I've been developing applications for over ten years. This book stands out as one of the best I've ever owned. It's very honest about how familiar you'd better be with PowerBuilder if you expect to use this book. The author takes into consideration the probability that you're new to Jaguar and yet doesn't 'dumb down' his guidance. It takes you through an explanation of CORBA, distributed processing, and gets you using Jaguar immediately. Excellent coverage of the administration of and development using Jaguar. If you plan on using EAS to build distributed apps, I highly recommend you read this book.

Excellant guide to getting started with Jaguar. Written for those users who know PowerBuilder and need to move to Jaguar. No distributed PB knowledge is required - Barlotta explains everything you need to know in plain english.

The time it will save you in figuring out what you are doing is well worth the cost of the book and more.

The examples in the book are good and source is available on line. The only complaint I would have is the code on the web is not organized in the zip file as well as it could be, but the author mentioned he was going to work on that. A little searching will find the code you need.

If you are thinking of doing distributed or web based applications using Jaguar, buy this book today.

This book covers most everything the wanna be Mac tech needs to know to be able to get into their system intelligently, without making expensive mistakes. It's not preachy or over technical from my standpoint, and it makes a great reference for when you need to tackle a problem yourself, rather than spending a lot of money for someone like me to come out and fix your computer.

I like the bredth and depth of the information given so much, that I am going to use it as the class text in my free Mac Troubleshooting class at Santa Ana College

This book is very good. It is one of the few books that is comprehesive of the entire Mac line (from the original mono-MAC to the iMAC). So many Mac books now only focus on the current models forgetting the earlier ones.

It is arranged by topic (memory, hd, input devices, etc.) and very easy to use. It is also suprisingly accurate. Twice I have found the information in the book's spec tables to be accurate where Apple's own ServiceSource specs were incorrect. (If only I had access to where they get their info!) :-)

Want to work on Macs? Get this book!

This book has really help me. It contains information about troubleshoting, installation, upgrade and more. Good graphics, easy to understand tables and easy to follow instructions.

Tremendous Trememndous. This book helped me upgrade my old SE-30 for use as a networked print server in my apartment. It got me set for networking 7 computers together on a LAN, including the fun ways that Macs talk with Windoze boxes and a Read Hat machine. I love this book!

Shortcuts, ways to speed up the machine, preemptive troubleshooting tips and more interesting info than you could ever retain.

If your Mac's out of warranty, you have nothing to lose by trying to fix it yourself. Stauffer's the man when it comes to clear explanations of needed repairs. I replaced the hard drive and CD-ROM drive following his book's advice. The book paid for itself.

There have been a couple of other books on message passing, but most of them have been anchored to a particular operating system or language. This book is the first to offer a general treatment of messaging, as a way to merge disparate middleware installations.

At the end of the day, messaging technology is just another way to allow distributed code to interact. Blunden takes the time to compare and contrast messaging against other distributing computing techniques. The result is that the reader can understands the relative advantages and limitations of messaging, so that they can use the right tool for the right job.

At every turn, Blunden grounds his explanations using concrete examples, so that the reader has a solid frame of reference (I can appreciate the author's humorous 10-page implementation of a DCOM server, basically to demonstrate how awkward a distributed technology can be... it's no wonder DCOM faded away).

The author of this book has obviously seen combat in the trenches. The fact that he would discuss deployment requirements like auto-update and secure network communication is proof enough.

I particularly enjoyed the bits of storytelling that Blunden hides in between technical discussions. In one part, he talks about working at a company in the throes of Y2K conniptions: "Like a 15-year-old kid studying for an algebra test, the company that hired me had waited until the last minute to do its homework. In September of 1999, the CIO put down his copy of Fortune Magazine long enough to realize that something needed to be done. Angry customers might file lawsuits, which would ruin the CIO's plans for a weekend cottage in Bermuda."

This book does an impressive job of looking at a "niche" of computer science and analyzing it in the backdrop of contemporary production requirements. The book provides an extensive presentation of background theory, a 10,000+ line working system, lucid documentation, and a discussion of alternative improvements and approaches.

To demonstrate the cross-platform/cross-language feasibility of his distribution, the author offers three different client pieces (C, Java, and Perl). This is a round-trip explanation of messaging passing that does a conscientious job of covering all the bases.

This is a very instructive learning-by-implementing book, in the tradition of Tanenbaum's MINIX. Blunden walks one through an in-depth analysis and implementation of a real message passing server.

I'm a little put off, though, by the fact that I find 10 5-Star ratings for this book, all posted on the same date by the same reviewer. C'mon.

I bought this book with the expectation that the Bluebox message server would be a token implementation.

Whoa! Was I wrong; this book shows the full monty! It includes a message server engine, a log server, a database interface, a license server, and auto update engine, recovery facilities, and a heartbeat monitor. Fortunately, the 100 or so classes that make up the distribution are well documented and a user manual is included in the book. The last few sections of the book also have some interesting anecdotes that are worth reading.