Software Books

The author explains vendor independent concepts of load balancers and discusses their (dis)advantages.

He is dividing them into four major applications:

* Server Load Balancing (63p)
* Global Server Load Balancing (19p)
* Firewall Load Balancing and (15p)
* Transparent cache Switching (8p)

additions:

* application examples (4p)
* future outlook (2p)

What makes the book so enjoyable to read is the authors love to the details. The story just flows very smooth.

Especially the thorough explanation, screenshots and technical details deserve the mark "distinction" (Very good). While I read the book it was like puzzle peaces suddenly falling all together to show me the bigger picture.

I did like the follow up of technical issues like session persistency (server affinity), URL switching, system design vs. functionality considerations and the limitations that come with the chosen solutions. The described issues are exactly those that system designers will face in real life and it doesnt stop there of course. The book is laying a good groundwork for development of advanced concepts.

The part of the book that I enjoyed most was the chapter about firewall solution concepts. As the author points out correctly the traffic flow in both directions must be managed. This is also why the setup from a redundant firewall to a load balanced redundant firewall must justify multiple complex issues.

In this case the author went through the analysis of the traffic flow, a stateful vs. stateless discussion, a layer2 vs. layer3 discussion, proxy firewalls, synchronized firewalls, multizone firewalls, VPN load balancing, active-active vs. active-standby discussion and the interaction between routers, load balancers and firewalls. While some topics could only be scratched on the surface the concepts and ideas behind it are explained very clear.

There is no doubt for me that a 2nd edition can easily just pickup where this edition left off. The author clearly shows that there are more scenarios to be discovered and discussed.

On the one side I would love to see a updated 2nd edition from the same author, on the other side I guess it's been held back to keep the competitions products in a distance ;-)

Also the book was published 6+ years ago I felt that the concepts did not loose any of its value. Which leads me to the point that this must have been " THE Technical Book of the Year 2002"

This book still receives well deserved full marks.

Bravo !!

if you are new to load balancing, get this book. Clear concept explanation, with diagrams. Highly recommend.

With his background in server products and networking products, this author is uniquely qualified with the product experience to present these topics.

From the simple beginnings of DNS server load balancing Kopparapu explains the driving forces behind and solutions presented to load balancing. The majority of the book is an introduction to the concepts and solutions available for server load balancing suitable for everyone from business casual to advanced technical users.

In addition to detailed explanations, the author demonstrates load balancing techniques through a number of illustrations. The illustrations are detailed enough to explain the concepts, but occasionally lack enough practical detail to go out and bulid in a lab or on a network without further understanding.

In combination with a good manual from a load balancing product, any reader would have enough information to implement sophisticated load balancing configurations.

In addition to server load balancing, the text covers caching techniques available through the use of some layer 4-7 devices. Of all the topics this one is the least detailed in the text. The author understandably covers only that part of cache technology related to layer 4-7 devices. A great deal of the technology required to put together an entire cache system resides in other parts of the system outside of the scope of this book. The implications for the architecture of a network are far reaching and worthy of at one more dedicated book on the topic.

Finally, the author presents the topic of firewall load balancing. Like caching, this is a complex topic. A complete understanding of network security and firewalls would require at least a few other books.

For those that already understand caches or firewalls though, this book provides detailed information on how to scale those systems with layer 4-7 technology.

This is certainly the most comprehensive and easy to read text on the topic. Anyone who reads this will also look forward to future texts from the author on emergning challenges in layer 4-7 network security and streaming content and distribution.

Compared with Tony Bourke's book, this one depicts more on technical details such as how packets flow, how health check is done and etc.. On the other hand, Bourke's book mentions more about the basic concept and the introduction to current available products.

If you are interested in how load balancers are designed, this is the right book for you. However, if you are just shopping around and only want to know what load balancers are, get Brouke's one.

Btw, I was a bit disappointed at chapter 9. I expected to see more opinions on the future development of load balancers but it was not mentioned too much.

This book is a very well written and nicely organised introduction to server load balancing. The author describes the basics of load balancing, including NAT, session persistence, and network architectures. A discussion on application-layer parsing was quite good. There is also a chapter on global server load balancing (including incorporating load-balancing into the authoritative DNS server) which I found to be very detailed and interesting.

Much of the book is centered on how to load balance TCP (and to a lesser extent UDP), and the author uses HTTP and FTP as his primary driving examples. Throughout the book, the author provides some insight regarding what approaches real companies use (e.g. "this method is what Foundry and Cisco uses."), which I liked very much. Also, the illustrations were plentiful (although a bit primitive-looking).

There are only a few negatives about this book. The english writing is a bit stilted at times, and the chapters on firewalls and caches were basically rehashes of earlier chapters. Finally, I was hoping the author would have provided more detail on the load-distribution heuristics (which server to choose) with more metrics and actual real-world results.

I found the book to be extremely well organised. You will not get lost while reading this book, but you will need a university-level understanding of TCP/IP (and probably the link layer as well to get the NAT material) and networks in general to fully appreciate the matieral. Overall, a great book.

This truly excellent book fills a large void in the software engineering and IT world - tying the business case to software. It is of paramount importance to demonstrate a quantitative, bottom-line impact when embarking on a software development or evolution project. Too few engineers and managers consider the full business context when making decisions. Many hard lessons in my 20 years of experience could have been avoided if I had the insights and techniques that this book provides.

I expect Mr. Reifer's book to be a classic in the field. It is chockfull of practical methods with worked-out examples of making the software business case. Not only is it rigorous in it's quantitative approach, but the author's broad and seasoned perspective helps practitioners steer through the minefield of people, politics and organizations. I seriously believe we would have more successful software projects if all technical people took on such a balanced view.

Don Reifer's book provides information not found in existing books on software engineering, process improvement, and project management. His primary audience is technical people who must sell a project to business people. In particular, he provides concrete, practical advice for selling a process improvement program. For example, Chapter 4 stresses the importance of focusing on cost avoidance instead of cost reduction to justify improvements. In Chapter 7 he suggests briefing middle managers individually to obtain their support. Based on my experience, this is sound advice because middle managers are often the most difficult people to convince in an organization. Giving personal attention to each manager pays big dividends later. He also suggests taking advantage of state tax laws to partially offset the costs of training employees. This is a win-win strategy for both the firm and the state. Training gives employees new skills and improves retention. This, in turn, helps the firm obtain more business and so generate more income for the local economy and more tax revenues for the state. He explains the difference between project and capital funds, and how to exploit this difference to obtain the resources you need. The book has many useful checklists. For example, one identifies the types and sources of information needed to prepare a business case. Another identifies the critical items to check when deciding to acquire a business.

His book will also be of interest to marketing people who are preparing sales presentations for complicated technical products. For example, these individuals could prepare business cases to compare possible alternatives. Even experienced managers unfamiliar with software products and process improvement will find the case studies useful.

Don Reifer illustrates the concepts presented in Part 1 with actual case studies in Part 2. These are based on his 30+ years of experience in the software field. The case study in Chapter 7 begins with what amounts to an engineering view of the problem and then the author provides comments indicating how a manager would like to see the information presented. This case study really shows the contrast between the technical and management ways of thinking. The case study in Chapter 8 shows how to assess the value of a company whose primary assets are intellectual property and knowledge capital.

Overall, the book is concise and well written. I was able to quickly absorb the concepts and techniques without spending a lot of time. It is a valuable addition to my reference shelf.

Making the Software Business Case: Improvement by the Numbers covers an area too few software engineers have any exposure to: financial modeling and business analysis, as it relates to the IT domain. Reifer's concise (300 page) book provides a broad overview of how the IT area appears from the business side, including critical material on how to frame technical proposals in business terms.

Amongst the many nuggets to be found in this book are:

· useful tips on where money can be found
· good insights into the politics of proposals and budgeting
· getting middle management buy-in
· countering executive challenges
· successful management of cross-project initiative dynamics
· software capitalization/depreciation
· Discussion of reuse from a cost avoidance perspective.

This book is not only good in terms of its material, it is also an eminently readable book in terms of style. Reifer elaborates his argument through the clever use of case studies that provide human interest and momentum to otherwise dry material. These case studies include:

· A defense contracting firm implementing software process improvement
· A public utility replacing an outdated mainframe-based transactional system with modern client-server technology
· An industrial controls firm suffering from moribund products
· A firm seeking to Internet-enable its internal systems

Reifert places strong emphasis on "making your numbers believable." He argues that this believability must address these nontechnical considerations:
· Cash flow
· Cost basis
· Cost/benefit
· Estimate fidelity
· Present value
· Profit and loss
· Risks
· Source of funds
· Tax implications

He does an admirable job in placing these concepts in context, and providing a clear overview of each.
The utility case study demonstrates the importance of understanding the overall financial dynamics affecting one's enterprise. For example, the differences between capital and expense budgets can be key in determining whether to purchase or lease equipment. As Reifert elaborates in the utility scenario, "Because this has been a profitable year, an increase in expenses [i.e. leasing as opposed to purchase capital expenditures] could have a profound positive tax consequence." The book has many examples of this type of valuable, integrated business insight.

Reifer has much sound general IT management advice mixed in with his financial message. A recurring theme through many of the discussions is the need for an executive sponsor, to provide political cover and tactical advice in forwarding the business case.

He also urges the reader to frame benefits in terms of cost avoidance rather than cost reduction-promising cost reductions often lead to the question, "OK, then who are we going to let go?" Not a good way to win friends.

I found his observations on the subject of central process quality assurance groups interesting:

"Reinventing staff organizations such as process and quality assurance groups is a good idea. Engineers assigned to such staff groups get stale once they've put in more than three years of service. Being in an audit and support role, they forget how hard it is to develop and deliver quality products under extreme deadline pressures." (p 137). The book displays a continual awareness of the need to balance these contending issues of cost, schedule, and quality.

The case study based on the industrial controls firm has an explicit architectural theme. This is an especially compelling discussion; software engineers are well aware how critical architectural decisions are, and how often they are compromised in the rush to write code. The discussion demonstrates how to make the case for architecture and include it in an overall work breakdown structure. Reifert is exceptionally creative in his case study creation, taking the opportunity to demonstrate hidden agendas, the pitfalls of contractor estimates, and developing a good working relationship with high-level consultants.

The book provides a solid summary of software estimation. There are whole books written on this subject, so the chapter is necessarily at a high level (although it does dive into some detail on the COCOMO II model in particular). However, it provides a valuable discussion of aspects of high-level IT budgeting beyond tactical project estimation, presenting numerous examples of cost breakdowns covering all phases of the systems development lifecycle, from architecture to maintenance.

The final case study moves into even more adventurous ground, discussing a company seeking to Internet-enable its internal systems via takeover (hostile if necessary) of a specialist firm. The ensuing narrative outlines the due diligence such a move requires, and the various tactical and strategic issues it may raise. A brief discussion of international intercultural relationships is excellent.

The book has only one minor flaw: it was obviously written during the dot-com bubble. There are frequent references to industry dynamics such as a venture-funded firm's survival depending on extreme time-to-market pressures, and perhaps an overemphasis on faddish Web technology.

This book is easily on my Top 10 software engineering book list. It provides a lucid, crisp overview of business issues that are all too mysterious to the average software engineer. Given the potential that well-architected, business-responsive software has to increase productivity, this volume is a service to both the software engineers and the enterprises that employ them.

This book is the aggregation of Mr. Reifer's extensive experience in software management and economics of reuse. His earlier books, "Practical Software Reuse" (ISBN 0471578533), and "Software Management" (ISBN 0769511007) evidence his experience, and probably account for the realistic approach he takes in this book.

Despite his technical background he takes a business-focused approach early in this book by explaining the difference between business and technical cases. Too many technical managers confuse the two, and this plus the other material in Chapter 1 explaining the fundamentals of business cases will set you on the right course.

Chapter 2 is the essence of this book, with advice on relating goals to metrics (using the Goal/Question/Metric technique), and the development and alignment of business cases to development life cycles. This is followed by two excellent chapters covering principles, rules, and analysis tools, and strategies. Much of this material is standard fare, but Mr. Reifer's clear explanations are better than most books that cover this material.

The second part of the book employs case studies that lead you through the development of a business case using principles, concepts and techniques given in the first part of the book. These reinforce part one of the book, as well as provide clear examples of business cases that work, and the process with which to develop them - including challenges, how assumptions were derived, and other nuances of which you should be aware.

The final part of the book is a single chapter on overcoming major barriers, and the sage advice is well worth heeding.

Overall, this is one of the best books on business case development because it is business-oriented, has an approach that is financially and tactically sound, and is written for technical-oriented managers in their own language.

This is not a book for software developers or managers who work in a small shop where there is focused development, little formal bureaucracy and a great deal of camaraderie. It is written for the person with responsibility in a large organization who has an idea for a major new project and needs to get it approved. Essentially, it tells you how to survive and thrive in a large organization that builds software.
The advice is fairly simple but quite accurate. Use numbers in your presentation that can be justified and are consistent with any previous numbers that relate to the project. Have solid data concerning the expected return-on-investment (ROI) from the project as well as any additional costs that may not be outwardly obvious. Quite accurately, the author is emphatic about the principles of present and future value. So much so that appendix B is just a set of basic compound interest tables. This is the most important advice that anyone in a large organization with a business case to plead can ever receive.
A lesser, but still critical point is that you must have a manager to champion your proposal through the managerial hierarchy. That champion must also know the expected ROI from the project very well, as upper echelons will consider a lack of knowledge on the part of the champion to reflect a lack of interest. Another point to reckon with is that if you receive the budgetary increase, it most likely means that someone else in your organization had theirs cut. Nasty, but also the way things are.
Finally, the author takes you through a case study as to when you should acquire a company rather than build a new internal division from scratch. His analysis of what to examine and consider significant is a solid strategy for determining which is the better option.
This is a book that really has two audiences, those who are lower level managers in large organizations with an idea for a new project and those who are starting a company and need to convince the people with the money to open their wallets. For them, it is priceless, but for all others it is difficult to see where they will find it of value.

This is great book, It has a lots of example and explained really well. Great Work!

The book is good but many solutions are not tested fully so its not that they can be cut and pasted directly out of the book. you may have to troubleshoot many of them. Otherwise a real good book.

As a Developer working predominantly with Oracle Databases for over five years, I'm always looking for books to help me produce better code. I have to say this is one of them. The author has produced a book that explains concepts in a practical manner that is also easy to read. I began reading this book just before starting a major development project and the code insights and examples assisted me greatly in this project.

Probably more a information and guidence book rather than a reference book. I found I read it from cover to cover and used the information as a platform for future developing. Some great code examples which I have used to great effect though!

With 15 years experience in Oracle as DBA and developer, I wrote a lot of packages and found in this book true advices and practical solutions, wich sound good to me. The best feature is that you can experiment all the code found in it and see by yourself the advantage of using the way proposed by McDonald. I like these books where autors breaks some common ideas ans show by "A + B" that the right solution is not the most common. A real useful book written by a true professional.

The book takes a bottom-up approach: the first part shows useful coding and optimizing techniques, while the second one gives real world applications and tips on program design.

I have two minor complaints, however:

Most chapters assume at least a good knowledge of PL/SQL and build on that, which I think is fair for a book titled "Mastering ...". On the other hand, two of the chapters (Triggers especially, and PL/SQL Debugging to a degree) take a different approach and start from the beginning, explaining the basics, too. It may be just me, but I think those pages are wasted.

Furthermore, there is a certain amount of overlap with Tom Kyte's Expert One-on-One Oracle, also from Apress.

The book got to me in a timely manner. I'm very pleased and hope to do well on the exam.

This certification study-resource from Author Amit Kalani, served as a rather indispensable part of the revision portfolio for Exam 70-320 (XML Web Services and Server Components with C# .NET ).

Simply put, it is a very useful & sound comprehensive reference for Exam 70-320. It served me greatly in gaining both an overview of all the elements that would appear on the 320 exam, but also served well in my overall review and revision endeavours for the 70-320 Exam.

using this resource got me to the place where i felt i had covered the core objectives for the exam and was ready to move on to the next phase ie: having a go at tackling past question scenarios.

i was glad i bought it.

what i liked about this book :
- it is a comprehensive read at 344 pages -(ie: the 2 Testing chapters non factored)
- there are exam questions after every chapter, relating to that chapter and the exam objectives the chapter tackles
- Answers with explanations are provided with every question featured in the book.
- there is a CD with questions set in an application that simulates the exam room scenario
- The CD also comes with a .pdf, e-version of the book.

I purchased the book in question as a pair with the companion Exam Training guide -(equally written by the same authors: Amit Kalani + Priti Kalani) from Que press ISBN: 0789728249; and i basically have'nt looked back one second since taking that decison.

the two books complement each other very well and provide a very fine balance between the need to train & equip the reader with the strong hands-on .NET XML Web-services development skills he/she will require in order to thrive as a C#.NET web developper; whilst at the same time fully framing these necessary hands-on expertise , in the context & framework of the exam the reader probably seeks to take at the end of working/ploughing his/her way through the book.

Amit Kalani is a very good author. he is well known in the C#.NET world. and he has a way of making a typically difficult material to teach, clearly explained, and he reinforces this with ample examples and practise, so it sinks in and becomes proper knowledge. So for those starting out on C#.NET or others looking for a place to start the preparation for the MCAD.NET with C# or 70-320 exam, these Books could easily serve as the spot to take it from.

However, i would add but the small proviso that depending on where you are along the previous "C#" programming-experience scale, i'd say you'd do well to buy yourself a good companion C# programming language text to accompany you on your journey.

There are lots of books on Amazon that would serve you well in this function/capacity . the text i used to give me a helping hand is called the: "C# Bible" by author: jeff ferguson (et al); it has for ISBN:0764548344.i found this easy to read and got through the first 20 chapters of concise, easy to follow, C# language basics, with relative ease.

After working through the 70-320 ExamCram resource in question and using the Training guide counterpart to acquire deeper hands-on practise to cement the interface between :( knowledge of the .Net Framework1.0 XML Web-services development concepts as treated in the books), with that of proper programming competence;(ie:knowing your stuff); I was ready for the next phase ie: going on to tackle past exam questions

using Transcender and the Testking more than sufficed to ensure & assure success at the exam;

Take & Ace the exam with ease: 150minutes & 43 questions.

Success at the exam-level is assured by appropriate preparation; ie: tackling past questions regarding .NET programming & C# XML Web-services development related problem scenarios in order to sharpen your wits about choosing the right solution in any given problem scenario. this is the crunch of it. do that ,and u pass.

End of.

The passing mark is 700 ie: 70%. i sat the exam on Tuesday (31st October 2006); scored 98% ie: 984.

MCAD.NET requirements accomplished!

Good luck.

cheers :-)

I used this book together with the corresponding Training Guide, by the same authors (this was redundant because the two books essentially repeat each other - I could have just used the Training Guide.) I think these authors are amazing - they have ability to present everything in such an easy understandable way, that I didn't just memorize the stuff for the exam but actually understood it. Now my next one is 70-229 - SQL server exam, I wish Kalani had a book for that one as well...

This book is pretty good at explaining the needed topics. I only used this book to pass the exam and found it compact and accurate.

Two bad notes are since coriolis was bought out it is tough to get errata for this book and there are a few problems. The securit section is a bit weak so read some online stuff to fill it in.

Good luck ZoOnI

I skipped reviewing the Microsoft study guide and used this book as my primary reference in passing the exam. Each component on this exam (web services, windows services, enterprise services) has its own architecture and interface. This book did a great job of distilling that information in a way that was easy to understand. I especially liked how the chapters were organized to introduce a concept, and then show you the code for implementing it. I simply wrote my own example for each chapter and did well on the exam. I didn't get much use out of the study guide or CD, but the practice tests in the book are very useful.

This book is very well written and easy to read. I enjoyed the experience much more than any I've had with MS press offerings. I am looking forward to more writings from this author.

There are a lot of IT guides out there but this is the one I can't do without. Superbly written, thorough and easy to follow. The labs are also invaluable and turn the words into real knowledge. I highly recommend this book for any IT professional's collection.

70-640 is a breeze after using this book just finished all of my certifications and this book made the 70-640 exam easy. I would recommend this book to my co-workers, friends and strangers alike. If you are prepping for the 70-640, this is all you will need to understand the content and pass the exam. The authors of this book knew how to gear the content to make it easier for you to understand and pass the exam.

This book is absolutely outstanding! They way the authors break down each section and give real world scenarios make this book unique. Given the changes in Server 2008 this book is a must have if you wish to pass the 70-640. After reading this book and using the CD I have passed the test and I know it was because of this outstanding book! I highly recommend this book if your goal is to pass the 70-640 while still obtaining a firm grasp on each concept.

The writing and delivery styles of Will Panek will grab and hold your attention throughout this book. Windows Server 2008 introduced numerous changes over 2003 and the author does a fantastic job of using real world scenarios and examples to teach them to you. Mr. Panek inserts humor in appropriate situations to keep your attention and make a point. If you complete this book you will pass the exam. I look forward to more from this great author.

This book has saved me a lot of time that I would have otherwise spent combing through huge Exchage reference books. As an Exchange Administrator, I have already found this book to be an invaluable asset in my reference library. Answers to many common administrative questions and "How To's" are easily found in this handy little volume. You gotta love its size.

Out of all the Exchange 2000 Server books I purchased, this one is the only one I used regularly. I have since purchased Stanek's Exchange Server 2003 book and it is equally as good if not better. For admins, it provides the essential details with clear, precise steps for implementing common features. For devs, it provides the cut to the chase info you need to get in there and get out quickly. I would recommend this very highly.

I bought this book for our Exchange admin when we were moving to Exchange 2000 from 5.5. Two months later I was going to be the one implementing Exchange and this book came to the rescue in a big way. As a total Exchange newbie I learned everything I needed (and now know) about Exchange from this book. Sure there are bigger books but not better books. If you are a Exchange guru, this book will be a little on the basic side for you. However, if you are anything less than a guru or if you are a new I would highly recommend this book.

I had a need to quickly resolve a problem with Exchange 2000 Server, having never worked with it before. This book was an excellent resource for that purpose. Not because it gave me the exact answer I needed (which I doubt many books would do) but because it clearly and concisely explained what you can do with Exchange 2000 Server and how to do it. It showed how to do things properly and from that it was fairly easy to deduce what was wrong.

Because the book is well structured (no excess verbage, no "chattiness") it's easy to read, clear and to the point. It gets to the point and stays on target.

All in all an excellent reference you'll use over and over and, I think, an excellent place to start learning Exchange 2000 Server. I find that this book tells what Exchange 2000 Server can do and how to do it. With that knowledge I think you'll be better grounded if and when you go for more in depth understanding of architecture and the like. After this book, if you want more in depth information you can move on to other (bigger) books but I think you'll get the biggest bang for the buck from this one..

This is excellent when used for quick reference and only for the experienced and knowledgeable. This is inappropriate for beginners since Exchange is intertwined with Active Directory. Without knowing all the implications of performing the various tasks outlined in the book, it can be detrimental to a company.

excellent reference material has been invaluable to me in the last week and has steered me into making some difficult choices easily

This book, especially if used in conjunction with the author's web site (see ASIN B0000C7RBX), is one of the most valuable additions to the IT security profession that I've read. My reasons for making this bold statement include:

- The book provides a coherent and focused approach to developing and implementing a security plan. You can find numerous books on writing and implementing policies and procedures, or establishing a security posture, but this is the first book I've read that steps you through the process of conceiving, implementing and keeping alive a viable security plan.

- By separating the process into three distinct domains (referred to as 'stacks') you ensure that your plan encompasses and integrates the technology, process and business elements into a coherent strategy.

- Artifacts in the form of a complete set of worksheets provide a set of tools that give a framework and speed up the planning process.

The planning approach set forth in the book is straightforward and realistic - you're led through the preliminaries, which includes conceiving a plan that matches your needs, and selling the plan to sponsors (an often overlooked, but essential activity when fighting for budget). The next step is to perform an impact analysis, and this is where the book shines, because the author focuses on business issues instead of technology. This promotes awareness and goes a long way towards getting buy-in and funding, as well as laying a solid foundation for a long-term security plan. Next the author shows how to select the correct security model and avoid common pitfalls. These lead to building organizational consensus - buy-in from all stakeholders. The difference between this step and the preliminary step of selling to a sponsor and obtaining funding, which is vertical, you need to promote the plan horizontally as well. The final steps are to implement and continuously refine the plan.

Of course, the overview above only describes the approach contained within the book. There is much more to commend it, such as clear writing, superb page design that portrays information in graphs, illustrations and tables, and the details the author provides. There is not a single statement or recommendation that is unsupported, and the material is both sensible and accurate.

The truth is, hackers and other attackers won't take no for an answer, and while there is absolutely no way to stop attackers from trying; there are ways to stop them in their tracks.

With that, Mission-Critical Security Planner is a surprisingly good book, aimed at someone looking to start developing their information security infrastructure. Rather than having to reinvent the wheel, the book provides planners with the framework and tools they need to create their information security infrastructure.

One good feature of the book it is large collection of templates and worksheets on various security elements. .../

The book is not overly technical and is quite good for those who need to get their security group up and running in a short timeframe.

For those that are serious about security, they will find that Mission-Critical Security Planner is like a cookbook. They can use it to prepare their security as needed.

Overall, Mission-Critical Security Planner is a very readable and useful book. Those who have an imperative to get their security groups up and running will find huge value in the book immediately.

In Mission-Critical Security Planner, Greenberg lays out all the security elements that should concern you and what questions you should ask about them. With this book, half the battle is won because you at least know how to do the planning. You still have to do the planning, but with the worksheets and tips provided in the book, that will be much easier than it used to be.

I read the book twice: once to get an idea of what all the worksheets were about and once to really read them with all the technical and practical details provided by Greenberg.

Greenberg identifies 28 security elements, including 15 fundamental elements, (six of which are core elements), and 13 wrap-up elements. Core elements include things like authorization and access control, authentication, encryption, integrity, nonrepudiation, and privacy. Those may seem obvious, but Greenberg has a lot of useful things to say about them that others haven't said.

Perhaps the most valuable part of the book is all the other elements, which we tend to forget, including addressing and routing (with tips on how to get those right from a security point of view), configuration management, directory services, time services, staff management, legal issues, and so on.

I'd be interested to see some projects get implemented with Greenberg's methods. I think it should work quite well, although due to entropy, laziness, over-worked engineers, and other such factors, I would guess that some of the numerous worksheets will fall by the wayside. But I think Greenberg would be OK with that as long as most of the worksheets are maintained and the company adopts security as a way of thinking.

In summary, this book is definitely worth reading, probably numerous times!

It is very rarely, that you'd see a good high-level security book nowadays. There are lots of great "worm-eye view" books with nice detailed descriptions of attacks, defenses, secure configuration options, tools and tricks. However, many of the high-level books resolve to quoting some outdated CSI/FBI survey, blabbering about security policy and giving out piles of outworldly advice on how to "mitigate risks".

This visionary book proves the opposite: you can have a high-level security book, which is not just practical, but actionable. "Mission Critical Security Planner" delivers a portion of the security process, packed into one toolkit. Make no mistake - this book is about planning how to do security, not how to tweak your scanner or configure a firewall. However, planning is indeed a critical (and, as the author points out, often missing) piece of security conundrum, and the book delivers on that.

An awesome component of the book is a large collection of templates and worksheets on "selling" security measures, planning the implementations, organizing security team, dealing with various business people and many other occasions. The book has the printed versions while its companion website criticalsecurity.com has the download.

The main part of the book is organized around "security fundamentals", large domains of security (such as authentication, encryption, integrity, privacy, etc), which are used to structure the security planning process, described by the author. For each of the fundamentals, the content is organized in sections: summary, security stack (covering various aspects from physical to application level), life-cycle management (from technology selection to response), business (on dealing with various categories of business people, such as suppliers and customers) and selling security (to execs, managers and staff). All of the above contain various templates.

Among the more fun parts, the section on negotiating with hackers is just exclusive and of the never-seen-before kind. Section in hacker profiling is also of interest, since it seems to originate from author's experiences (and not in just reading about it on the news). The book also demystifies such elusive notions as "impact analysis", "security ROI". PKI also has a prominent role in the book. While PKI (as it is defined today) might or might not fly, the book gives a great example of large-scale production implementation, running for many years. Another great feature of the book is author's "future 10 attacks list" with his predictions on threat landscape.

Overall, the book seems indispensable to those responsible for securing networks. Security managers and CSOs will likely gain maximum benefits from using it (due to the book targeting), but other security professionals will benefit as well. Notice, that the benefits can be derived from "using" it as opposed to just "reading" it, although even the latter will prove highly enlightening. The "selling security" templates alone are likely worth their weigh in gold. The book is well-written and, while not possessing the lively style of some recent security books, will beat some of them hands down in real-world applicability. After all, even if you very well know that IDS is valuable, who will help you to "sell" it to the CIO? This book just might!

Anton Chuvakin, Ph.D., GCIA, GCIH is a Senior Security Analyst with a major information security company. His areas of infosec expertise include intrusion detection, UNIX security, forensics, honeypots, etc. In his spare time, he maintains his security portal info-secure.org

This book is clearly written and user friendly. Biafore gives links to information sources, making it easy for the reader to get more information on each of the hacks. These links alone are worth the price of the book.

I've been trading for over twenty years, including a period as a floor trader on the Chicago Board of Trade. Even with that experience there are tips and tricks in this book I found useful to the point where I employ them daily. To be complete as a reviewer I will say there is a lot of pretty basic stuff from my point of view, but still well worth reviewing since some of it I had forgotten.

Well written, easy reading, well organized

Online Investing Hacks is an excellent introduction to the world of investment. Though the title does contain the word 'Online', I would say that the general information the book provides on investing is not limited to the online realm.

Overall, I was very happy with the book, and found it incredibly useful. Though I do have several investments (401K, some stock, mutual funds etc) I would hardly consider myself an authority on the subject. This book provided very detailed explanations and tips on various forms of investment, from CD's to Index funds, and everything in between. While the experienced investor might not glean much from reading this book, anyone just getting started will find it an excellent reference, and resource.

The format of the book is similar to the other books in the 100 * Hacks series published by O'Reilly. There are exactly 100 hacks, or topics, which are spread across 9 chapters. Each one is an individual entity and can be read and understood without reliance on any of the other hacks.

One minor annoyance I had with the book is that it is geared toward those of you who, for some reason or another, run Microsoft's Windows OS, or have access to Microsoft Excel. Luckily, of the Excel examples that I played with, Open Office's Calc program handled them with minimal tweaking.

I can easily recommend this book to anyone who wants to invest, but is unsure of what to invest in, or needs some tips on making the most of preexisting investments. Those of you who enjoy research and building your own stats and graphs will also find parts of this book rather intriguing, as it covers data acquisition and manipulation with Excel in great detail. It will make an excellent addition to my reference shelf, and I have a feeling it will be well thumbed through in a very short time.

It seems like everyone is involved in investing in some form or another. While I always felt like I should be investing too, it was never clear to me how to begin this process. After all, it's my money. How can I be sure I'm investing in something that will provide some sort of reasonable return? This book is an excellent resource in answering some of those questions and putting the new investor on the right track.

This book is written in the same format as the other "hacks" series by O'Reilly. This format is very easy to read, and the format makes it very easy to find answers. Rather then having to read the book from cover to cover, the reader can pick out topics they are dealing with, read the answer, and move on. Since many of the people interesting in a book of this nature will likely have little time, the book's format works to its advantage.

The book begins with some basic introduction to the stock market and tips for selecting appropriate stocks or mutual funds. The whole middle section of the book deals with data analysis. The author discusses how to understand a company's balance sheet (e.g. what that P/E ratio means), how to spot companies in financial trouble, how to pick a good stock, and even how to trade. There is also a good discussion on minimizing the effect of taxes on your little return on investment.

The author even goes further and gets into a discussion on financial planning. In addition to discussing debt reduction, the author also talks about IRA plans and different strategies for saving for your child's education expenses. I think my favorite part of this book was the discussion on different education savings plans. The author discusses the ins and outs (as well as tax consequences) of each of the plans, and provides some examples illustrating the fact that it's better to start saving earlier than later.

This is an excellent book, not just for its investing advice, but also for its sound financial planning. This is a great book for anyone who is interested in increasing their wealth, saving for a rainy day, or simply saving for future financial goals.

Online Investing Hacks by Bonnie Biafore (O'Reilly) is one of those books that can pay for itself in short order, as well as over and over.

Chapter list: Screening Investments; Hacking Excel for Financial Analysis; Collecting Financial Data; Analyzing Company Fundamentals; Technical Analysis; Executing Trades; Investing in Mutual Funds; Managing Your Portfolio; Financial Planning; Index

I worked at Enron from 1998 through 2001, and spent plenty of time during that dot.com era following my stock portfolio. I watched my Enron stock value go from incredible value to a point where it cost more to sell the stock than it was worth. I won a few bets (face it, that's what they were) on a few dot.coms and lost many more. What could have been an incredible nest egg, isn't. This book would have been a lifesaver if I had read and paid attention to it a few years ago. Biafore shows you how you can analyze and invest wisely using a variety of tools available to everyone.

If you're an Excel user, you'll find it an invaluable tool for analysis. She'll show you how you can use it to create financial charts (#13), calculate compound annual rates of growth (#26), and use rational values to buy and sell wisely (#36). #39 - Spot Hanky Panky with Cash Flow Analysis (using Enron as an example) would have literally saved me hundreds of thousands of dollars had I known about it. Even if you don't care about the investing tips, the hack on downloading data via Excel web queries (#7) was something I didn't know how to do (or that you could even do it!). The book has a little something for everyone.

As with all Hacks titles, you probably won't be interested in every single item. Some may not be applicable to your situation or may be too complex for what you care to handle. But all it would take is one hack to work out and change your investing for this book to pay huge dividends. If you do your own investing, you owe it to yourself to get this book.

I definitely recommend this book for anyone working with OpenGL's new Shading Language. I would, however, say that probably the most difficult part of working with GLSL is getting it working in the first place. Especially on Linux, this is somewhat confusing - some cards support GL 2.0, some don't, but still support the GLSL if using the ARB function calls. I would also make sure to point out to new users that GLEW is close to essential when working with the GLSL - you can download it from sourceforge. It might be worth mentioning in future versions of the book, along with ARB functions which are the same as the GLSL standard functions shown in the book.

I'm not a fan of the 'group of papers' style of book. But this book pulls it off nicely. The text is consistenly good throughout. And the illustrations and formulas are high quality and presented nicely.

I would have liked full color throughout, but I accept that it would have been cost prohibitive on a book of this heft. Speaking of heft, yeah, this is a doorstop of a book. I think some of the text could have been edited down and the formatting tightened up to reduce bulk.

The recent trend in graphics hardware has been to replace fixed functionality with programmability in areas that have grown exceedingly complex (e.g., vertex processing and fragment processing). The OpenGL Shading Language has been designed to allow application programmers to express the processing that occurs at those programmable points of the OpenGL pipeline. Independently compilable units that are written in this language are called shaders. A program is a set of shaders that are compiled and linked together. The OpenGL Shading Language is based on ANSI C and many of the features have been retained except when they conflict with performance or ease of implementation. This shading language is without a doubt the most important addition to OpenGL since its inception, and this book provides an excellent guide to programming with it. The author was one of the primary contributors to the development of the language, and he provides a well-written and insightful explanation of the language and its use.
The book begins with a review of OpenGL basics, followed by an introduction to shaders and how they fit into the pipeline. It then covers the language itself, including data types, operators, interaction with the OpenGL state machine and fixed function pipeline, built-in functions, and more. It also introduces and explains the OpenGL APIs needed to use shaders.
The last half of the book focuses on shader development, including general process and workflow, and coverage of many specific techniques, such as procedural textures and GPU-based animation. It even includes a section on implementing the fixed function pipeline using shaders. The book ends with a handy comparison of OpenGL Shading Language with other shading languages, such as Cg, HLSL, and Renderman and a couple of appendices providing a language grammar and API reference.
I particularly liked chapters 6 through 8, which take you from a simple shading example -"brick"- through the specific steps of shader development that you would need to master regardless of the API you are using. Also the chapters on procedural textures and noise and the accompanying code examples helped clear up some matters that were murky when I read "Texturing & Modeling: A Procedural Approach" by Ebert et al. In summary, I highly recommend this book to anyone interested in implementing software shading, both from the standpoint of OpenGL and from the standpoint of the design process itself. I notice that Amazon does not show the table of contents for the second edition, so I do that here:
Chapter 1. REVIEW OF OPENGL BASICS
OpenGL History; OpenGL Evolution; Execution Mode; The Frame Buffer; State; Processing Pipeline; Drawing Geometry; Drawing Images; Coordinate Transforms; Texturing;

Chapter 2. BASICS
Introduction to the OpenGL Shading Language; Why Write Shaders?; OpenGL Programmable Processors; Language Overview; System Overview; Key Benefits;

Chapter 3. LANGUAGE DEFINITION
Example Shader Pair; Data Types; Initializers and Constructors; Type Conversions; Qualifiers and Interface to a Shader; Flow Control; Operations; Preprocessor; Preprocessor Expressions; Error Handling;

Chapter 4. THE OPENGL PROGRAMMABLE PIPELINE
The Vertex Processor; The Fragment Processor; Built-in Uniform Variables; Built-in Constants; Interaction with OpenGL Fixed Functionality;

Chapter 5. BUILT-IN FUNCTIONS
Angle and Trigonometry Functions; Exponential Functions; Common Functions; Geometric Functions; Matrix Functions; Vector Relational Functions; Texture Access Functions; Fragment Processing Functions; Noise Functions;

Chapter 6. SIMPLE SHADING EXAMPLE
Brick Shader Overview; Vertex Shader; Fragment Shader; Observations;

Chapter 7 OPENGL SHADING LANGUAGE API
Obtaining Version Information; Creating Shader Objects; Compiling Shader Objects; Linking and Using Shaders; Cleaning Up; Query Functions; Specifying Vertex Attributes; Specifying Uniform Variables; Samplers; Multiple Render Targets; Development Aids; Implementation-Dependent API Values; Application Code for Brick Shaders;

Chapter 8. SHADER DEVELOPMENT
General Principles; Performance Considerations; Shader Debugging; Shader Development Tools; Scene Graphs;

Chapter 9. EMULATING OPENGL FIXED FUNCTIONALITY
Transformation; Light Sources; Material Properties and Lighting; Two-Sided Lighting; No Lighting; Fog; Texture Coordinate Generation; User Clipping; Texture Application;

Chapter 10. STORED TEXTURE SHADERS
Access to Texture Maps from a Shader; Simple Texturing Example; Multitexturing Example; Cube Mapping Example; Another Environment Mapping Example; Glyph Bombing;

Chapter 11. PROCEDURAL TEXTURE SHADERS
Regular Patterns; Toy Ball; Lattice; Bump Mapping;

Chapter 12. LIGHTING
Hemisphere Lighting; Image-Based Lighting; Lighting with Spherical Harmonics; The *erLight Shader;

Chapter 13. SHADOWS
Ambient Occlusion; Shadow Maps; Deferred Shading for Volume Shadows;

Chapter 14. SURFACE CHARACTERISTICS
Refraction; Diffraction; BRDF Models; Polynomial Texture Mapping with BRDF Data;

Chapter 15. NOISE
Noise Defined; Noise Textures; Trade-offs; A Simple Noise Shader; Turbulence; Granite; Wood;

Chapter 16. ANIMATION
On/Off; Threshold; Translation; Morphing; Other Blending Effects; Vertex Noise; Particle Systems; Wobble;

Chapter 17. ANTIALIASING PROCEDURAL TEXTURES
Sources of Aliasing; Avoiding Aliasing; Increasing Resolution; Antialiased Stripe Example; Frequency Clamping;

Chapter 18. NON-PHOTOREALISTIC SHADERS
Hatching Example; Technical Illustration Example; Mandelbrot Example;

Chapter 19. SHADERS FOR IMAGING
Geometric Image Transforms; Mathematical Mappings; Lookup Table Operations; Color Space Conversions; Image Interpolation and Extrapolation; Blend Modes;

Chapter 20. REALWORLDZ
Features; RealWorldz Internals; Implementation; Atmospheric Effects; Ocean; Clouds;

Chapter 21. LANGUAGE COMPARISON
Chronology of Shading Languages; RenderMan; OpenGL Shader (ISL); HLSL; Cg;
Appendix A. Language Grammar
Appendix B. API Function Reference

Twenty years ago, I used to program graphics on an Evans and Sutherland PS340. It was then one of the top of the line graphics computers (costing $100k). It could labouriously do shading, but only Phong and Gouraud. Nowadays, many PCs have this ability, and much faster. But a problem still persists, where often the shading methods are restricted to what is implemented on the graphics chips.

In contrast, you have the approach in this definitive book on OpenGL Shading Language. This lets you implement in your code, shading routines of your own devising. To be sure, given the same shading method, one done in this language, and one in the hardware, then the latter will have better performance. But it turns out that today's computers are fast enough, and have enough RAM, that the difference in response might not be appreciable.

The book describes an extensive set of built-in convenience functions that come with the language. And the language's API is explained in detail. The author rightly recommends that you come at it with some experience in the standard OpenGL.

Since the language is still quite new, you are more or less on your own, when looking at development tools. This dearth is expected to be remedied in a few years. But right now, you'll have to rely on your wits. Along with a chapter that gives general principles of how you should develop your own shader. What may be even more use, however, is the second half of the book. Devoted to case studies of many shaders. Understanding these may be more beneficial than any IDE.

Oh, as you might expect from a graphics book, there is a lovely set of colour plates in the middle of the book, showing what custom shaders can do. Treat it as inspiration if you wish.

The OpenGL Shading Language is without doubt the most important addition to OpenGL since its inception, and this book provides an excellent guide to programming with it. As one of the primary contributors to the development of the language, Rost provides a clear and well-written explanation of the language and how to use it.

The book begins with a review of OpenGL basics, followed by an introduction to shaders and how they fit into the pipeline. It then covers the language itself, including data types, operators, interaction with the OpenGL state machine and fixed function pipeline, built-in functions, and more. It also introduces and explains the OpenGL APIs needed to use shaders.

The last half of the book focuses on shader development, including general process and workflow, and coverage of many specific techniques, such as procedural textures and GPU-based animation. It even includes a section on implementing the fixed function pipeline using shaders.

The book ends with a handy comparison of GLSL with other shading languages, such as Cg and HLSL, and a couple of appendices providing a language grammar and API reference.

If you're doing shader development with OpenGL, you'll definitely want this book on your desk. My only complaint about it is that it was written before GLSL was officially promoted to the core. When that happened, a number of important things were changed that aren't reflected in the book. However, determining the differences isn't difficult, so don't let that deter you from picking this up.

The book was so useful that we (LDEQ) had Michael visit us for a week. It was great having you here.

This handbook is extremely helpful to the novice Discoverer User. I appreciated the ease in locating specific items that I needed help with. It is user friendly and very enlightening!

I bought this book recently to understand some advanced features of 10G and also get more hold on admin tasks and setups.

I am not through with the entire book yet, but whatever i have red till now is really well written. All features - desktop and admin are well explained with examples and screen shots. Notes at the end of items provide special remarks which are very useful as well.

A very helpful book for beginners as well as advanced users.

This is THE book to get for Oracle Discoverer. What more can I say, it's well written, clear with good examples.

Oracle Discoverer is a complex tool and much more than a single understanding of the functionality is required to use it effectively for business intelligence.

Armstrong-Smith has achieved this goal in a pragmatic book that not only shows the "how" but the "why", with simple illustrative examples from real-world systems.