5 comments about Java Message Service (O'Reilly Java Series).

1. If you're looking to learn JMS, then this is a decently good book to get you started. One of the best things about it is that it's not very thick and it gets to the point pretty quickly.



2. The basics were covered, but I felt this book was a little outdated. There werent alot of books to choose from so I chose this book because it seemed like it had the most coverage.



3. This is a reasonable good book, as you can expect from O'Reilly. There is a good introduction in the topic (e.g. where is Messaging used for, what kind of messaging does exist, what is JMS), and it offers chapters with some practical code how you send and receive messages, and so on. It contains real Java code with excellent explanation.
   
   If you're familar with Java, don't know anything of Middleware and JMS, this is a pretty good start. If you read this book, and you play with an free open source JMS implementation (e.g. ActiveMQ), you will soon get things working.
   
   *HOWEVER* This book is now arround 5 years old and *ONLY* covers JMS 1.02, where JMS 1.1 is now common.
   
   *BUT* the majority of all other JMS books are also 3-5 years old, and some also covers only JMS 1.02.
   
   If you keep this in mind, I think this is a pretty good purchase.



4. As a beginner to JMS, I found this book to be very useful. Most chapters have examples and the book also gives you the link where you can download code for the examples. The examples are simple and clear for the most part (except in couple of places) to illustrate the concepts related to JMS. I tested the code on BEA Weblogic Server and it runs fine without any problem. There are some minor errors in one or two examples but they can be spotted readily once you read the book and you should be able to fix them with relative ease. Overall I found this book to be a nice introduction to JMS. However, as another reviewer mentioned, keep in mind that this book is now more than 5 years old and JMS has been updated since then. Still it is a good buy if you are new to this topic.



5. If you are looking into JMS for use at work or you are just curious, this straight-to-the-point and easy read will start you on your way. While not going into absurd depth about the topic, the author provides a wonderful overview and core knowledge transfer for the reader.
   
   Quick and easy to read, this no-fluff title will give you everything you need to get started with JMS.
   
   If you are a beginner, this will get you started off with an extremely solid foundation. If you are a pro, it will give you a great "step-back view" of the methodology that you are utilizing.
   
   Good for all, but recommended as EVERYONE'S introduction to JMS.

5 comments about Multithreading Applications in Win32: The Complete Guide to Threads (Addison-Wesley Microsoft Technology Series).

1. I bought this book to get advanced concepts of win32 multithreading which I cant get by browsing through msdn. Although this book has covered all topics, I was expecting more like a "Concurrent Programming In Java, by Doug Lee" kind of book which has a lot of gotchas. I would recommend this book for beginners looking for examples of how to use the APIs. Advanced developers should look somewhere else.



2. This material is still relevent, even when using .NET. The discussion of Win32 multithreading transcends any particular development environment used with a Windows 32 bit environment.
   
   The key idea behind this book is getting correct, reproducible results with windows multithreaded applications. Multithreaded applications are very hard to get right and even harder to properly test. The author explains the many sources of problems and how to avoid them.
   
   In order to understand this book's code samples, you will have to understand the Win32 API and code written in Visual C++ for Windows NT. It is important to see examples of these concepts in code.



3. Quite useful book. But I wont recommend it. Other than file I/O and threading, it is not for advanced programmers.
   
   From the beginning to end, it only imparts about Win95 and WinNT. None of the OS after Windows 98 are covered. So, much of information covered is obsolete.
   
   I was looking to a complete multithreading book for Windows XP, COM threading models, writing perfect multithreaded GUI application.



4. It does a very good job at describing the Win32 API for multithreading but the applications of multithreading assumed is strictly I/O related (Networking,printing,writing/reading files). The set of techniques for parallel processing on the same data is completely absent such as data organization in memory to optimize its parallel access. This is probably due to the age of the book as when it has been written, single core processor system was the norm. Parallel processing will become very important with the growing popularity of the multi core systems. Despite this weakness, this book is still my best recommendation for learning multithreaded programming on Windows since, to my knowledge, there is not yet any book tackling the subject of parallel processing on a Windows/x86 platform.



5. A beginners guide to multi-threading on WIN32. Experienced developers might find it useful to quickly skim through this book to see if there is anything that they didn't already know, but for the most part anyone with significant experience should find a different book.
   
   The language used in the book is very easy to read, making life easy for newcomers to threading, but possibly woolly enough to be slightly dangerous too, in that some stuff could bits could be misinterpreted. Developing example code using incorrect practices and then slowly fixing the problems is informative, but possibly not the best way of doing things. Why not just go for the right way first and then point out the errors that could have been made? That way it is safe for people to dip into the book and use code as is, rather than having to trawl through for a correct version. Talking about using code from books - do the authors expect the reader to trust their code when they include comments like "This happens occasionally instead of end-of-file. Not sure why" ? Certainly, that means that I would code-review anything I lifted from this book very carefully. More likely, it means that I won't lift anything from this book and will use Jeffrey Richter or Richard Gerber/Andrew Binstock instead.
   
   The book does cover a large range of Windows-related multi-threading topics - from file handling, GUI handling etc through implications for DLLs. It touches on Sockets but only very briefly, which was disappointing. Also particularly disappointing were the chapters on debugging and inter-process communications. There are too many books around that say that testing/debugging multi-threaded code is difficult without coming up with good strategies for overcoming the difficulties. Unit testing, logging and the debugger are useful, but obvious. "you must start making predictions (otherwise known as guesses)" (p268) is certainly an approach, but perhaps the time has come to use an engineering approach?
   
   The material could do with updating, as Windows, C++ and development techniques have all moved on since this book was published. Experienced developers should look forward to Jeffrey Richter's new book, planned for end of 2007, which should be as up to date as it comes.
   
   Despite referring to the CD-ROM the book didn't actually come with one. Instead the source had to be downloaded from the Addison Wesley web-site. Strangely, Addison Wesley do not have an errata for this book on their web-site. Normally I'm a big Addison Wesley fan, but they have done a few silly things with this book. The very first page of the preface had me concerned, when they hyphenated _beginthread to be _begin-thread. Given that this book is aimed at beginners I would be pretty sure that someone, somewhere tried typing that into their computer complete with the hyphen.

5 comments about The Verilog® Hardware Description Language.

1. Was sharing this book with my workmate. Found it pretty useful. I think its a great reference book to have.
   It has
   + A great Index.
   + Good examples.
   + Been written by the masters of Verilog.
   - A lot of words (ie some people might find it very 'wordy')

   Every ASIC/FPGA designer I know has this one in there shelf. So go for it.




2. The claim that this book has become the standard for learning Verilog is true.
   I use Verilog a lot but I still wish I had read this book before writing Verilog codes.



3. This book should be used only by the experienced users that can filter out problematic sections.
   Major problems:
   - first chapter, "recommended" by authors for university courses, is extremely chaotic (begin..end blocks are called loops, exercises ask you to use loops before introducing them, etc.)
   - cover of the latest edition claims coverage of the latest Verilog standard - unfortunately it is very poor coverage: new interesting features such as libraries and configurations are not mentioned at all!
   - I had to work hard during many trainings to correct bad coding styles showing in students reading this book as their first Verilog publication
   - the book is grossly overpriced...

   Main advantage:
   - good set of examples




4. 'The Verilog Hardware Description Language' is a very good tutorial and reference for intermediate designers.
   I used this book in an upper level hardware design course. The course had a beginning Verilog course as a prerequisite. I hadn't taken that course but I had experience in digital design and VHDL. This book got me up to speed quickly with it's many examples and tight explanations of the Verilog Language.
   Some pluses:
   -Example designs are short, complete, and simulatable. Most are even synthesizable. This is good because an example can be quickly understood in its entirety. You don't need to flip through and stare and multiple pages to get an idea of what's going on. If you insist on having them, there are two long, practical examples towards the end of the book.
   -The text is very well written. Similar in style to 'The C Programming Language by Kernighan and Ritchie.'
   -Verilog 2001: Focuses on 2001, which is a little clearer than previous standards. I think all tools support 2001 by default now so that should be used.
   
   Some minuses:
   -Too expensive.
   -Not enough discussion on how Verilog constructs are compiled and netlisted. This is critically important in FPGA/ASIC design. However, this book is not any worse than other HDL books in this respect. It's just so important, I really haven't seen anything that gives the topic the treatment it deserves.
   
   Possible minus:
   -Not really for beginners. This is not a hardware design text.
   
   I haven't used the CD that came with the book so I can't comment on that. My guess is anything on that CD is not as good as industry standard tools like Mentor's ModelSim.
   Overall a very impressive book that will get you to productivity quickly in a Verilog project.



5. I really liked the book since I had read a copy from my school library hence I decided to purchase one. Unfortunately since Amazon doesn't set any standards that all sellers should meet, my purchase was a rip off.
   
   I order the book assuming it was a North American Copy Unfortunately The one that I received was printed in CHINA & FULL OF GRAMMATICAL MISTAKES please watch out for the seller "Express_Textbook" do not purchase unless u want a Chinese Version.
   
   The seller does not specify this information so once you have made a transaction you'd have to go through the hassle of returning it.
   
   A NOTE TO AMAZON ADMIN: PLEASE INSIST SELLERS WHEN SELLING NEW PRODUCTS TO SPECIFY DETAILS SO THAT CUSTOMERS CAN MAKE THE RIGHT CHOICE.

5 comments about .NET Test Automation Recipes: A Problem-Solution Approach (Expert's Voice in .Net).

1. This is an excellent book. The contents are very helpful and organized very well. The author does a great job explaining the usage of the code examples and teachs how to write UI Automation.



2. .NET Test Automation Recipes is a fantastic book for manual testers looking to get into automation. Dr. McCaffrey breaks down how each section of code pertains to the test at hand. I even e-mailed Dr. McCaffrey a question about a section and he sent an answer within the SAME DAY!!! I work at Microsoft and I've had serveral colleges try to steal this book from me. Great purchase for testers and SDETS.



3. '.NET Test Automation Recipes: A Problem-Solution Approach' by Dr. James McCaffrey is one of the finest books that Apress publishes. Employing a great writing style, great topic to write about, brevity (less then 400 pages), and well balanced chapter breakups of material (12), I found this book to be highly enjoyable and a must buy for anyone that is looking to add efficient testing into their software environment!
   
   If you are in QA or develop tests where you work, you owe it to yourself to pick up a copy of this book for your .NET testing work. This is an outstanding book that teaches, references and explains a topic that is well worth the time!!
   [...]



4. If you know to program in .NET this maybe a good book. But of course if you know to program, you will be a developer and not a QA person. If you are in White Box QA the explanations maybe a little deficient. I recommend a good beginner .NET programming book before you attempt anything on this book.



5. This is by far the best book on software testing automation that I found. There are some very good books about software testing principals out there but here is the first book that shows in really simple terms exactly how to write the testing code. Highly recomended.

5 comments about SAP NetWeaver For Dummies.

1. I got this book to get myself more educated on what SAP Netweaver is all about. I've been doing SAP consulting for over ten years but, like others, feel like I'm not up-to-date with the latest SAP Technologies and products.
   After carrying this book around with me for over two months, I'm still not done with it. This is because I keep on getting irritated when I read this book and then I put it down. And I'm not easily irritated. I think I'm at the point where I'm going to put it in a box (with many other books that I DID read) and read something else instead. This book is just wasting my time.
   
   Here's my problems with this book:
   1. The writers try to be funny/entertaining all the time. I do like humor, but they do it way, way too much and they are not funny at all.
   2. Some of the things they discuss are simple, basic, worthless information that any IT person knows.
   3. They make Netweaver seem easy, all-good and the future of IT. I love SAP and I think Netweaver is probably a good platform. But I think this book is overselling it and making unproven claims that may mislead less-experienced people.
   
   This book could have been good if the (useful) content was offered in a different way. Some suggestions if a second edition materializes.
   1. Don't try to be funny. Just present the material.
   2. Leave out all the unnecessary, useless information. You're not obligated to go over 400 pages. I'd prefer to read a thinner book with just the relevant information.
   
   I don't always give the lowest rating for things I don't like. And this book does have some useful information here and there. But the presentation is just so terrible to me that it makes whatever good it has worthless.



2. While the book's attempt at humor irritates me, I still manage to find good information. The author covers a lot of material. Some of it is way too simplistic. Some of it is not deep enough in my opinion. I've picked it up a few times and put it back down, but won't toss it. That being said, I'm still looking for seomthing better (SAP Press doesn't have anything actually good either, despite some new titles).



3. 1)I might have sat with the book if not for their jokes
   2)The terminolgy used in definitions and in examples is different.
   3)Repeating stuff that is not at all useful.
   4)The paragraghs of repition wont work but i dont understand how the pictures also dont work
   5)I sincerely request the authors to stop writing text books.



4. This is the first "for Dummies" book I have read and I was very pleased. The authors did an excellent job explaining all of the elements of SAP NetWeaver and how they inter-relate. As a business executive trying to get my arms around the technology, this was exactly what I needed. It will be valuable reference for the future, as well.



5. Buy the book if you like, but for me an ABAP programmer w/10+ years experience it was just fluff. A couple hundred pages of hearing how great Netweaver is and what it could do, w/o actual hands-on is not IMO what a 'Dummies' book is meant to be. The included CD was even less.

5 comments about Beginning MySQL Database Design and Optimization: From Novice to Professional.

1. I was hoping that there would be more about designing databases. Though I was pleasantly surprised at the solid introduction to MySQL that the book gives. In fact it spends the first two thirds of the book on the basics, before getting into optimization and finally programming.
   
   The design aspect of the book is in the third chapter, which is one of the books best. There is some good high level material on the fundamentals of schema design, and then material on relation mapping, and then into it's implementation in MySQL.
   
   There is a lot to like in this book. And I like the fact that someone is finally giving some attention to MySQL, which, if it's not the most advanced database in the world, is probably the most ubiquitous. This is a fine book for anyone who works with MySQL.



2. If you already know the basics of MySQL, then this book can be a nifty boost to your productivity. The authors plow straight into giving good tips for better table design. For example, the first chapter covers MySQL basics. But it furnishes very understandable advice. Like never using spaces in identifier names. While MySQL permits this, it greatly increases chances of logic errors.
   
   Later in the book are far more complicated tips. Crucially, on how to optimise complex queries. While SQL notation is standard across vendors, each database has different ways to best phrase queries. So since you have committed to using MySQL, it helps to know what are best here.
   
   The authors also instruct in how to hook up to external languages like PHP, Perl and Python. (What is it about all these languages that start with P?) Each has its adherents and is quite popular. So they try to give coverage of the combinations with MySQL.



3. The first three chapters of this book deal with the basics of MySQL including basic concepts, column and table types, keys, indexes, and normalization. The authors have written an excellent introduction to MySQL that provides all the core information you need to start using it right away. The chapter on finding the bottlenecks is one of the best sections in the book and details some of the finer points to be considered when creating your database. On the other hand, the part on optimizing queries is excellent for the beginning MySQL student (which is the target audience for this book) but not as good as it could be for the more experienced MySQL user. Perhaps I am just more sensitive to this area because of all the badly done queries I have had to deal with before. A good understanding of just this part can make a tremendous difference in optimization. If you are new to SQL queries the authors have done a great job of explaining why this is important and how to understand it when a query takes under a minute to run and then after a small change takes twenty. The last section covers accessing the MySQL database via other programming languages such as PHP. Beginning MySQL Database Design and Optimization is a recommended read for its target audience - the beginning MySQL programmer.



4. As a beginner to MySQL I bought this book to gain an insight into the how's and why's of using MySQL. Overall having read the book from cover to cover ( a first for me as far as computer books go ) I can thoroughly recommend this book to anyone new to using MySQL. The layout is clear, the text easily readable, not too techie at first but still a great deal of examples for you to get up and running.
   The writing style is easy going but not preaching and all topics are treated in an easy to grasp manner.
   The only down side is that it doesn't cover programming MySQL using Visual Basic although several other languages are covered well.
   Overall a great book for the newbie and intermediate user.



5. As a working professional database developer/DBA, I should have noticed that every other review about this book is at least three years old, most almost four. This book was written to be used with MySQL V4.0, with look-aheads to 4.1 and 5.0. Version 5.0 has been released for almost two years now, and V6 is on the near horizon. A lot has changed in terms of optimization and feature sets. I sincerely hope that the authors will consider updating this work so that it is more current in terms of tuning and features. If you are new to MySQL, use the book as a basis for solid SQL and design principles; if you are more experienced, perhaps just reading and studying the 5.1 and 6.0 docs from MySQL AB would serve you better.
   
   Lee Parmenter, CMA

2 comments about Getting Started with Flex 3: An Adobe Developer Library Pocket Guide for Developers (Adobe Developer Library).

1. I am new to Adobe Flex development, but I have been a Microsoft web programmer for many years. I really enjoyed this book; it's an excellent intro to the world of Flex development. I love the length of the chapters they are just long enough to finish in a quick 20 min break during the day. The authors do an excellent job demonstrating what can be done with the technology. The examples are simple but well thought out and well written. They start off by showing the reader real world applications already in place on the web. In the following chapters he provides examples that introduce some of the controls available in Flex. The examples are labels, buttons, checkboxes and datagrids just to highlight a few. One chapter walks the reader through creating a Runner's Calculator. The last chapter contains a nice list of websites, blogs and community resources to get you into the developer community.
   
   If you are new to Flex this is an excellent book to start with it's both informative and a quick read.



2. I'm sure most of you have had the experience of having a smart friend try to teach you how to do something only to wind up feeling frustrated, stupid or both. This was my experience with this book. Often an expert too easily forgets what it's like to be an absolute beginner and either moves too quickly or leaves out important steps. I admit I wasn't expecting a thorough exploration of Flex in this tiny guide. This was my first 'pocket guide', so perhaps I'm being unfair or expecting too much. But I felt the author just leapt from one thing to the next without offering enough in the way of explanation or context. What the book IS good for, in my opinion, is giving you some idea of the things Flex can do. But you can get a very good idea of what Flex can do at Adobe's website- for free. To anyone new to Flex, I would suggest finding a free way of checking out what Flex can do. Then, if you're interested, go and find a different book to really get a proper start.

5 comments about Practical MythTV: Building a PVR and Media Center PC.

1. The book is outdated for the state that mythtv has advanced to. I used MythDora to set my system up and most of the hard work has been done. There are also areas that the book does not cover. I actually found the book to be not be worth the money.



2. I fall within the vast range of Linux users who know just enough to be dangerous, but at least realize that this is where they happen to be.
   
   I purchased this book brimming with enthusiasm and confident that with its assistance, I'd have no problem getting MythTV up and running.
   
   In fact, my experience with this book was very ungratifying and downright frustrating.
   
   To start with, I found that many of the command lines cited in the book just plain didn't work. In some cases, it was easy to discern where the commands strayed from reality, in other cases not so much. These discrepancies might arise from my using a later version of Ubuntu or MythTV than those to which this book was written. Frankly, I don't know.
   
   I was also frustrated to find that while the publisher provided a web page for users to report errata, it was a purely one-way - You're free to leave your comments, but don't expect a compilation of earlier postings (or corrections)to be made available in exchange, and certainly don't look for any sort of response.
   
   In the end, I set this book aside and installed Mythbuntu - Ubuntu and MythTV all rolled into one ISO package, and searched the web to resolve the myriad of issues and tweaks that had to be addressed. This was not the outcome I would have preferred, and what I was hoping to avoid when purchasing this book, but at least I've managed to get my crate up and running from scratch.
   
   If you are already very strong in Linux, this book will easily give you the guidance you need, but otherwise, caveat emptor.
   
   For what it's worth.



3. I have been using Windows for as long as it has been around. I have done web development. I have even been exposed to Unix a number of years ago, so I thought I would be able to follow directions in this book and be successful. Ubuntu was easy to install and looked like a good product. However, the directions in MythTV did not work. I finally gave up after installing Ubuntu five times and starting all over again. I even purchased a Ubuntu manual thinking that would resolve the problems I had. Unfortunately, it did not and I finally gave up and re-installed Windows XP on my computer and BeyondTV. That did work. I was reminded that Windows does make some things simple that the Unix platform still makes somewhat difficult. I would not recommend the book. I plan to give it away... The Open Source "Open Office" worked great on Ubuntu as it also does on Windows, so I judge MythTV or this books directions to be the problem.
   Cecil Denney, Maple Grove, Minneapolis



4. If you are interested in getting a Mythbox up and running, this is a great book to start with. True, all of the information you need is available on-line, but here it is organized and at your finger tips. The book is clear, well written, well organized, and reasonably complete and accurate. Things change very rapidly in an area such as this, but this book provides a great foundation. If you are willing to use the Ubuntu distribution and MythTV version that is used in the book, things should go well.
   
   One thing to look out for, if you are new to Linux their recommended procedure for compiling from source will be a bit of a challenge. They do NOT tell you what you have to do to be able to compile something from source. There are many packages that need to be installed above and beyond the standard Ubuntu install. However, I just used Synaptic to install the version of MythTV that is available as a Ubuntu supported package and things went fine.
   
   Well worth the money and highly recommended.



5. Look, I'm not going to say that these guys didn't try, or that this is a cynically written attempt to cash in on something, but this book is as close to worthless as I can imagine.
   
   Now, again, this is not entirely the authors' fault. MythTV is highly dynamic. What's true today isn't true tomorrow. I'm a journeyman MythTV builder, and a lot of what I've learned in the painful progress I've made simply does not apply any more.
   
   That said, a lot of stuff =hasn't= changed, and it's here where the book falls apart. They should have started with the basics of content flow, i.e., where is the media coming from? Because that's the first thing you need to know before you even decide if MythTV is right for you. (Over the air content, for example, is easily handled by Myth, while controlling a set-top box from a cable, satellite or fiber optic company is a whole 'nother kettle of fish.)
   
   While support has been added since this book was written, the stuff they actually did mention that has been part of MythTV since its incpetion is not well covered. For example, to set up your MythTV backend, you have to select from various capture card types. There are V4L, MPEG2, DVB, etc.--how about explaining what these are? No explanations is the norm, and when there is an explanation it's often simply restating the on-screen text without actually clarifying.
   
   Six months of having this book and I've never once found an answer to a question I had. Now, I don't go looking for product specific stuff, because (as I said) there's no way they could cover that, but just basic joints and cogs and so on.
   
   See, the thing about MythTV is that if you have just the right hardware and a simple enough setup, it might take you fifteen minutes to set up. If you don't, it could take you weeks to set up, or you might never be able to do it.
   
   To be useful, this book really should have explored =how= to troubleshoot. They couldn't do the actual troubleshooting for you--there are too many things that can go wrong--but they could tell you about the utlities and hardware settings that allow you see where your problems lie.
   
   Maybe they just didn't have the space. But, as I say above, it makes the book almost completely worthless.

5 comments about The Success of Open Source.

1. I'm a commercial software developer, and found the author's history of the UNIX culture and the story of its evolution into what we now call Open Source to be fascinating. That alone made it a good read for me. Add in the thought provoking analysis of the "whys" (the real point of this book), and it's a killer combo.
   
   Warning: the book is *full* of sentences like "Pluralism at many different levels is being enabled by communications technologies and by experimentation with property; together, these are reducing the marginal cost of adding voices toward an asymptote of zero." Despite that, I've been able to read it at the pace of a thriller, not a textbook.



2. For the serious reader (and who indeed thinks open source is hilarious?), Weber provides a detailed history of how this idea developed. He traces it from the advent of unix in the 1970s, and the generous (ie. low fees) licensing terms by ATT. Which led to the BSD Unix that flourished in the 80s. Also during this time, GNU took off.
   
   But the bulk of the book deals with the 90s onwards. Especially as linux grew from Torvalds' seminal contribution. Its intellectual roots in unix and GNU are studied. We also see the rise of the Free Software Foundation and Apache, as articulate enablers and promoters of open source. All of which was aided by the invention and meteoric growth of the Web. This played a vital role in enabling a global audience of programmers to hear of and contribute their efforts.



3. Steven's book brings a rich articulation of the social practices innovations unleashed by the Open Source collective: a new understanding of private property that better fit the tech forces and the challenges of the present. His book it is not a model; it is not the list of the 10 reasons why...; it is not the defense of an emerging theory; but an historical account in which anecdotes, facts, historical moment, tentative hypothesis, set the background to allows the reader to reshape her/his own questions. The book gave me a perspective I have been testing with IT architects, programmers, software designers...I feel myself much more prepare to engage in conversations about the future in a meaningful and effective way. Thanks to the author!



4. The Success of Open Source in a not a just wistful paean to Linux as the title would suggest. Rather, it is two books in one.
   
   The first book is one of the very best recapitulations of the open source movement and all of its predecessors. The second book is about how something that just seemingly shouldn't work, works so well, and how those principles behind its working extend to more than just the open source movement.
   
   The author, a university professor, draws liberally from the traditions of historians, economists, sociologists, and psychologists to paint a compelling picture of why the forces behind open source are not going to go away any time soon. Read in best companion with The Cathedral and the Bazaar, which IS a bit of a wistful paean to Linux, it illuminates its subject wonderfully.



5. I loved this book. It covers the history of Open Source and explain WHY people do open source and HOW they make it happen!

5 comments about The Definitive Guide to Stellent Content Server Development.

1. 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.



2. 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!



3. 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!



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



5. 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.