Programming Books

Now in an expanded and updated second edition, Signals And Systems With MATLAB Applications by electrical engineer and educator Steven T. Karris is an invaluable textbook and resource especially written and organized for students of electrical engineering. An easy-to-learn-from text, with practical MATLAB applications to use and drive the theory home, Signals And Systems authoritatively covers a wide selection of mathematical and engineering topics in seasoned and technical detail, including delta functions, the laplace transformation, fourier series, analog and digital filters, and much more. Signals And Systems is a confidently recommended advanced instructional resource especially for dedicated students or veteran electrical engineers looking to brush up their basic skills.

I found this text to be very interesting. It contains material that I have not seen in a single book. All theorems and definitions are well and simply expressed and illustrated with practical examples. I've found few but insignificant references to equations and figures, and I've informed the author. It is an ideal text to learn both the material and MATLAB. Appendix A
is a very good introduction to MATLAB and it helped me very much.
M. Phillips

Awesome textbook.
wish I found it early enough to not by the course's texbook.
Unlike many others that I have been forced into purchasing for classes, this books explains everything down to a T, along with graphical representations on every page!
Another great thing I really appreciate is the fact that the text/math is spread out nicley, making it easy to highlight and take you own notes (which I do all the time, and find it very helpful when reviewing). The fashion in which the material is presented is free of leaps and bounds which I have found is not the case at all for many other signals books. I was quite happy to find that in this case I paid less for a better book. I have since ordered the electronic devices book as well from the same author/publishing-company. Thanks Steve!
-pat

Easy to read. Good balance of just enough theory and an ample amount of examples and problems to test one's knowledge. Can be used as either a main textbook or as a supplement for self-study. Perfect for those looking to use MATLAB as an integrated study tool.

The author's discussion of the material is excellent. He presents good examples and tries to integrate proofs or theorems into what he has told you.

Unlike many engineering books, he actually puts solutions in the back of the text.

This is a refreshing change from publishers who tend to keep this information "restricted".

When you are working with a higher level subject such as Signals and Systems, you want to build practice with problems.

Another point I especially enjoyed was the clear discusion of state space analysis in both the laplace and the Z domains.

I picked up this book because we recently started a project where management uses the term "SCM" a lot, and I had no real idea of what that means. This book provides a great overview of the ideas and genesis of SCM, and why it is useful. It also provided lots of detail and examples about the ideas presented to really cement them in my mind, and translate them to activities that we currently do. I can have an intelligent, scientific conversation about SCM now, which is exactly what I was looking for. This book is really excellent.

The book is an excellent addition to your SCM library. This should be you first read if your just beginning in Software Configuration Management. The author covers the descipline well in this easy to read edition.

This book is the second edition A Guide to Software Configuration Management (ISBN: 1580530729). The change in name is a bit confusing, but the author explains why the name was changed--due to the change in scope, magnitude and coverage of the book.

Apart from the changed title, the most endearing features of the first edition--simple language, clear explanation of the fundamentals and lucid treatment of advanced topics--are still there. The first edition was a book that would get you as quickly up-to-speed on the basics and key issues. The second edition builds on the first edition. The language and writing style is still simple and easy to read. The fundamental concepts and the basic SCM functions are explained in clear and jargon free language. All the good aspects of the first edition are retained. But the chapters are revised, updated and enlarged to include the latest developments and to give a more thorough, comprehensive and in-depth coverage.

The chapter on SCM standards is an excellent primer on the various military and commercial SCM standards. The strengths and weaknesses of each standard is explained. The comparison of four representative standards- EIA-649, IEEE Std-828, ISO 10007 and MIL-STD-973-is very useful and informative. The chapter "Software Process Improvement Models and SCM" gives an overview of various SPI models like CMM, CMMI, ISO SPICE, BOOTSTRAP, Trillium, etc. and explains the role of SCM in process improvement with the help of the SPI models. The chapters on SCM plans, SCM organization SCM tools, SCM implementation, SCM operation and maintenance, SCM in special circumstances give sound and practical advice on the various aspects of SCM from SCM system design, to implementation, operation and maintenance.

In addition to providing a sound foundation on the SCM fundamentals, the book is an easy-to-digest reference to various practical aspects of SCM that are not found in most books and manuals. It is a virtual toolbox of information that can be readily put to use by the SCM practitioners.

The first four chapters of this book might be called: "Why do Software Configuration Management." And they are excellent. If these explanations make sense to you, you might implement SCM before you look around at the software project and find that part of the source code is missing, the source code of this sub-routine doesn't match the binaries, this bug that was fixed is back, and any number of other problems.

The next several chapters go into the fundamentals of SCM. This includes such things as the mundane definition of configuration numbers and the reports that need to be issued.

Just when you are getting to the point where you know that this can't be done, the book goes into the SCM automation tools that are available. Chapter 16 talks about the general functions that can be performed by the SCM tools. Finally he gives a list of the most popular high-end SCM tools. (Mr. Leon - in the next edition of your book I'd like to see some comments made about each of these tools. Just a short sentence or two would be nice to help me narrow down the list of likely suppliers.) For low-end (and low-cost, even free) tools, he points you to the cmcrossroads.com web site for a comprehensive and frequently updated list of suppliers.

This book is a valuable introduction to the whys and wherefores of software configuration management. It will tell management what can be expected and if you're assigned to the task, it will get you well started.

I am the CEO of a software company and even though I knew the importance of good SCM practices, as a small company, we procrastinated on actually implementing anything formal. Anyway, when the fires got to a point, we decided it was time we took the medicine to get serious about SCM and I turned to Mr. Leon's book for help. I also sifted through a bunch of other books on the topic at libraries and bookstores and was immediately overwhelmed by the seeming complexity and all the jargon. The simple language, the concise explanations and the organization of content in Mr. Leon's book served as almost a how-to-manual for me as we went about implementing SCM concepts in our organization. I bought a couple of copies of the new edition for my two EPMs and they have been unanimous in their praise of this book as well. If you're looking to bring some order into your software development world through SCM, I would highly recommend you start with this book.

This is a terrific book on what it takes to make web applications really work (both for users and for the businesses that create them). Managers of web design projects should read this book for its eminently practical advice on documentation, workflow, and pitfalls to avoid. Highly recommended.

If you're new to building web applications and want a balanced perspective on the engineering challenges involved -- from understanding user needs to data modelling to scaling gracefully -- this book is a great place to start. It's mostly language-agnostic, so it'll be a good starting point for a few years but won't update you on the latest technology. Nevertheless, I know very few web developers who wouldn't learn something important from a careful reading of this book.

Where this book really shines is as a bridge from the world of college Computer Science to the world of actually building applications people use. This transition encompasses understanding your users, making flexibile designs, considering security, aesthetics, and a host of other issues one does not actually learn in a normal college CS curriculum. Thanks to its project focus, this book (and the course curriculum it implies) seeds an awareness of these many issues that can later be developed through experience. Other "software engineering" books over-emphasize theories, but this one will actually press you to get stuff built.

It's not easy to build a really good online community website. There are a lot of things to think about, and many of them have little or nothing to do with technical programming skills.

Buy this book, read it, step through it, and learn from some of the best teachers on the subject. And then when you've learned what they have to say here, take your new-found skills and build your own online community site. Using the methods in this book, your web sites can be more useful, successful, and profitable.

To Philip and Alex's Guide to Web Publishing, I learn of this new chapter in Mr. Greenspun's (et al) effort to encourage the Web to be all it can be. This volume is plainly a text book, designed as a practicum, and with its completion my understanding of how to achieve what's possible now and conjure the future of the Web will be greatly furthered. I'm finding it inspirational in the process of designing; expand your dream's horizons!

This book is helpful for programmers as well as people who work more generally with technology. I'm using very specific, technical information from the "Adding Mobile Users to Your Community" chapter for a web application I'm building, while using concepts from the chapter on discussion forums for a research project on how discussion tools are used at my university. If you build web applications, or work with people who do, I highly recommend this book.

You may find the articles in this book one by one from the net, but it's always good to have a all-in-one product.

For anybody involved in teaching classes on Project Management, this book is an excellent reference. Broad focus, enjoyable and informative reading...

This book is a collection of numerous classic articles on software project management. It is well organized and it is clear that a great deal of effort was put into identifying the best articles to include in this collection. The reason I give it 4 stars instead of 5 is for what it doesn't have -- an index! Without an index you will have a difficult time finding specific information without scanning many pages of text.

This book provides a broad but detailed look at the functions and activities necessary for the proper management of a software development project. It is what you would expect from IEEE, an academic perspective on the process---both from a quantitative development and quality management orientation. Some of the contributors are, of course, priceless (particularly Alan M. Davis' "Trial By Firing: Saga of a Rookie Manager") in relating their own experiences as project managers in this strange business we're in.

This collection was so good that I went back and ordered the other two collections (Software Engineering and Software Requirements Engineering). For anybody who teaches Software Engineering or Project Management classes (or anybody wanting a broad knowledge of the subjects), these books are invaluable.

This book is the best book on software project management available for three reasons: (1) it talks to the basics of what makes a successful project and manager, (2) it describes what does not work in a software project, and (3) it walks through practical steps that can be used on real software projects to solve real process problems through the complete life cycle. The book is well written, concise and does not subscribe to any fad methodology or proscribe any silver bullet solutions (smart work and attention to detail are the only effective methods). In fact, the author spends much time debunking industrial myths. There is a good section on cookbook solutions and an example project included as a learning tool. I use this book on the job and highly recommend it.

Unlike most text books, it is a very easy to read book allowing one to read it from cover to cover. The book is an excellent source for novice project managers who need a guide to the many aspects that come with the job. Personally I refer to it often for suggestions on which documents I should produce or what actions to take while managing a project.

This book covers Software Project Management broadly with a lot of good information for both the new project manager as well as the old hand. The material is presented as a comprehensive overview rather than a detailed instruction. By itself the book does not go deeply enough into any of the areas to provide a novice with enough useful information so it's a good book to use in conjunction with books providing more detail.

Despite its lack of detail, the book presents many important points - the importance of the human equation, analysis/organization tools such as Tony Buzan's MindMap, having a Management Information Center, and using standards without having a programmer's revolt. There is only passing mention of key issues such as scope creep, the tendency of management to try to throw more personnel at a project in trouble, needing to build testing into the initial design process, and the pro's and con's of the various development methods (waterfall, spiral, etc.). A number of references are quoted, including many IEEE documents (IEEE is the publisher) plus books by Gerald Weinberg, Capers Jones, Tom Demarco, and other recognized gurus - which make good adjuncts to this handbook.

Phillips perpetuates one of my pet peeves, the issue of including the top ten risks in the risk assessment document. What if there are only 7 risks which seem to be significant? What if there are 12? Granted, it would be unwieldy to track & evaluate dozens of risks routinely, but it doesn't make sense to suggest that exactly 10 be tracked.

The discussions of Configuration Management are quite lengthy and in a bit more detail than other topics covered.

Although the book is fairly short at 500 pages and is easy reading, there is a substantial amount of information covered. The 5 star rating is for the breadth of information covered, with the caveat that other references would be needed by those unfamiliar with the concepts presented.

Don't confuse the ease of reading this excellent book with the depth and power of the information within it. Being involved in software project management myself, I related to the ideas the author expressed and feel I have learned much from reading the book. Other project managers in my company are now reading this book and share similar opinions.

The book contains good explanations of various techniques for formalising projects. It also contains a number of case study experiences which are very apt.

I recommend this book to project managers of all levels and to managers of software companies.

This is a well written book for the people interested in succeeding with software project management. The author spells out the key pit falls to software development and offers realistic solutions. There are many up to date helpful graphics and tables throughout the book. This is easy reading and keeps the reader interseted.

This book has quite good coverage of topics and simple to follow.
References and follow-up/conclusion were useful.

I've maybe three or four books on the subject of software security and this is the best so far. Very concise and well organized and covers just about every facet of software vulnerabilities that I've ever heard of. Very helpful too because at the end of each chapter it gives detailed advice on how to avoid the vulnerability that they dicussed. Also, the CD comes with some nice tools and source code. I definately learned a lot from this book and highly recommend it to both web application and desktop application developers.

Every month, hundreds of security vulnerabilities and warnings are announced. Although they cover a wide set of products and programs, the underlying reason for them is generally the same: insecurely written software. When software is written in insecure code (which includes most software programs written today), serious security flaws are inevitable.

The Software Vulnerability Guide was written to help software developers acquire the methods necessary to write secure code and find existing problems in current software. After making a persuasive case for secure code in part one, the book progresses into the areas that are crucial to writing secure software.

Part two of the book covers system-level attacks and details important topics such as passwords, scripts and macros, and dynamic linking and loading (DLL). Part three plunges into attacks on the software, exploring heady concepts such as buffer overflows, format-string vulnerabilities, and integer overflow vulnerabilities. Most of these attacks have been known for decades but are only receiving wide-scale attention now.

Further chapters delve into securing data and Web servers. For each of the vulnerabilities mentioned, the authors describe how they occur and how to prevent them.

An enclosed CD-ROM contains software examples described in the text, plus various open-source security software testing tools, including Ethereal, Nessus, and Nmap. Any business serious about writing secure software should ensure that all of its code writers receive a copy of this book

Herbert H. Thompson and Scott G. Chase's Software Vulnerability Guide comes from a security director and a security architect, drawing upon their combined expertise to consider techniques developers need to use to produce secure code in modern software. Developers and testers receive both tools and assessments of tools designed to help recognize and prevent common vulnerabilties in source code. Commentary and code examples pack a guide which includes a CD-ROM with source code and many tools described within.

If you consider yourself a solid developer but know you probably don't give the security of your software/databases as much attention as you should, then you need to get your hands on The Software Vulnerability Guide.

Unlike a lot of other security books, this one isn't full of a bunch of vagure generalities. It gives you solid details on some of the most common (and perhaps some less common) holes that exist in the software you just released. The information contained in each useful chapter is easily digestable by beginners.

Buy the book and spare yourself the embarrassment from some twenty something who stole some script off the web and deleted all the data in your intranet application.
[...]

This book uses Smalltalk to teach the basics of object oriented programming on Mac or PC. Before getting my hands on this book I have to say I was having trouble grasping the basics.

I personally bought the book as I want to learn Smalltalk. For some reason the "with Robots" in the title had me skip over this book for almost a year. Most, if not all the other Smalltalk books I got, although great, usually assume differing levels of pre-existing programming knowledge and experience and approach the teaching of Smalltalk skimming over the stuff that is a required foundation to *understand* it. Stephane Ducasse does an excellent job of explaining that missing foundational stuff. And he does it without getting too deep into Smalltalk or Squeak itself.

As others have pointed out this book is not really focussed on teaching Smalltalk - Smalltalk is the tool used to teach basic O-O programming. However, he's done an excellent job of doing both!!!

Having finished this book I'm writing basic programs - and finally understanding better the programs of others.

The use of an Integrated Development Environment [IDE] for a user to learn a language in, and to then program within, is well known. Microsoft has made powerful IDEs for its languages. And the open source Eclipse can be used for Java. Along these lines, Ducasse offers his book. It teaches Smalltalk using the Squeak IDE.

The twist is that Squeak uses the visual metaphors of robots and robot factory, to convey the crucial concepts of objects/classes. As Ducasse explains, Squeak can be directed at an audience that is perhaps of high school age or even younger. So a clear visual feedback between example code and what the student sees then happen is vital, given her limited background and possibly limited attention span.

Squeak uses Smalltalk in part because that is a very minimalist language. If you come from C++, Java or C#, you may be struck by its simplicity, compared to the oodles of classes and notational intricacies of those languages. Which of course also makes it easier for a young student to learn Smalltalk or Squeak itself.

I wonder a little about the book itself, though. A motivated high school student could easily use it. But for some younger students? In that situation, it may well be that the book could be best directed at a teacher, who can then instruct from it.

I whole-heartedly recommend this book for introducing the novice to the nature of computing. I am giving a copy to my 14 year old grandson to introduce him to the fascinating world of programming. He lives 500 km away from me, so he will largely be on his own. I do not expect this to be a problem because the book is perfect for self study.

I want my grandson to learn the essence of computing without spending time on things that he will have to unlearn later or that prove to be blind alleys on his road to computer proficiency . This book is ideal for this purpose. It will let him experience the basic notions of computing in carefully graded steps. Each step tells him how to do fun experiments in the provided environment where he directs a robot/turtle to draw interesting patterns on the screen. The 22 steps take him from a simple sequence of commands to the creation of elaborate simulations; ending at the point where my grandson should start creating his own classes and subclasses.

The experiments are all done in Squeak, a dialect of Smalltalk. It could be argued that my grandson had better learn Java or some other mainstream language. I believe Smalltalk is a better choice because it is simpler, cleaner, and more immediate. The basic concepts are universal and my grandson can easily switch to some other language after he has mastered the fundamentals.

The book is written in a fluent, idiomatic English. It is written in the first person; the writer speaks directly to the reader. This writing style combined with the examples being concrete makes for the smooth communication of what are really abstract ideas.

Anybody wanting to understand more than e-mail and text processing could not do better than to install the free robotic environment on their computer and work through the book’s text and examples.

I've used this book and the BotsInc environment to show my 12-yr old daughter how much fun writing software can be and it's been a wild success!

In fact, it all fits together so well that I'm planning to use it as the basis of an introductory series of classes on software writing as craftwork, to be offered through a local craft organization.

Help train the next generation of software writers! Buy this book!

This book actually teaching computer programming, rather than teaching a computer programming language. It has to use something, and Smalltalk (Squeak) is gentle enough that it doesn't get in the way of the topic.

Stéphane Ducasse, a prolific writer about object-oriented programming, says in his preface: "The material for this book was originally developed by my wife, who is a physics and mathematics teacher in a French school where the students are between eleven and fifteen years old". Indeed, the pains taken to make object-oriented programming understandable to someone with no background are quite apparent, and they certainly pay off. The author has more than met his goal "to teach you object-oriented programming, because this paradigm provides an excellent metaphor for teaching programming".

Instead of teaching Smalltalk, the computer language he uses, he's actually teaching programming. Smalltalk, originally designed as a teaching language, has minimal syntatic issues and it very simple once the student knows a few basic rules. The reader of this book doesn't have to know much to start workign though, since the author distributes a working Squeak environment that's ready to use. He's already provided a "Bot factory" and a working (virtual) robot to which the reader can send commands, much like the LOGO language and its turtle. Without getting caught in the details of object or class design, the readers start out simply by interacting with objects and sending them messages to control their behavior.

As the reader learns more about what the robot knows how to do, the author devises trickier problems for the reader to solve. These usually involve causing the robot to move in such a way as to draw out a pattern. In doing so, the reader is actually writing programs that control the robots behavior to accomplish the goal. Although the language is really SmallTalk, the author effectively hides most of that through the use of the robot's little language.

The Squeak environment the author distributes is easy to use for anyone with a basic idea of computers (i.e. mouse and keyboard, click here, and so on). It's easy to install because you only need to download it and click on the file. From there, you see the Squeak environment and a ready-to-use robot. Move the mouse near the robot and a speech bubble with a blinking cursor appears. Type a command and the robot responds. Easy peasy.

If you are already a computer programmer, or have some experience with computer programming and want to learn Smalltalk, this book is probably too basic for you. However, if you go to the authors web page (Amazon tends to edit links from reviews, so google the author's name) you'll find links to many free Smalltalk books that you can download as PDFs.

then get this one. I learned enough about the reasons for using it and also how to configure it to authenticate against an LDAP server.

Well worth getting and keeping on your shelf.

Squid: The Definitive Guide by Duane Wessels is a great book for someone with aspirations of setting up and getting the most out of Squid. It is lengthy at just over 400 pages, but that is to be expected and desired in O'Reilly's "The Definitive Guide" series. One point worth mentioning is that Duane Wessels (the author, for those with short synaptic cycles) is the one who started Squid and still works on it today. Each chapter builds nicely on subsequent chapters, so there isn't any skipping around. If you're just looking to set it and forget it, this book is probably not for you. Otherwise, read on.

The first three chapters are pretty basic: history of Squid, downloading then installing. For those with no concern of going through downloading and installing, there is a nice section describing each configure switch and, while weighing in at a healthy 48 options, it may be helpful to have this as a reference.

Chapter Four, Configuration Guide For the Eager, is an often desired, but often left out chapter in technical books. By just reading chapters one through four, it is possible to have a fully functional setup of Squid, albeit not very secure or ready for the pounding of the masses. You will, however, begin to understand how Squid operates. This chapter discusses the most often used settings, such as: minimum/maximum size of cached objects, log files and ACLs to restrict addresses, etc.

Chapter Five, Running Squid, covers what you expect. It includes such topics as, boot scripts, chrooting and rotating log files. Again, basic stuff, but necessary for the sake of completeness.

Chapter Six, All About Access Controls, covers one of Squid's major powers and attractions, access controls. ACLs give the administrator extremely fine-grained tuning. Some of the choice highlights for limiting access to addresses/domains include, but not limited to: filter by subnet, MAC, IP address or administrator assigned group. Furthermore, regular expressions can be used to filter URLs or URIs. A most likely seldom used, but very cool, feature is the ability to filter by BGP AS (Border Gateway Protocol Autonomous System) numbers. HTTP request methods such as POST, PUT, DELETE, etc. can also be filtered. Filtering by time or restricting access by user name is also supported. Each topic is assiduously explained and leaves little to be desired.

Chapters Seven and Eight cover disk caching with chapter Seven being basic material and then Eight covering more advanced topics. Discussions on object pruning, size limits, cache replacement policies and many other cache optimizations are covered in these chapters and are necessary to thoroughly understand if you are situated in a relatively large environment or just want to squeeze every bit of performance from your Squid.

Chapter Nine, Interception Caching, covers transparent proxying. This chapter discusses the benefits (no need to configure clients) and drawbacks (cannot do user authentication) of implementing such a system. It then goes on to discuss how to configure Alteon/Nortel, Foundry, Extreme Networks, Arrowpoint, iptables, pf and ipfw to perform the routing to the Squid box.

Chapter ten, Talking to other Squids

Scalability is another favorable attribute of Squid. Running in parallel with previous chapters, this chapter details the advantages (load balancing and increasing your cache hits) and the disadvantages (security problems with having to trust neighboring Squids) of a caching hierarchy. In addition, it explains how to configure connect timeouts and other tweaks to keep Squids aware of when their siblings are down.

Chapter eleven, Redirectors, covers another great attribute of Squid. Redirectors can be used, among other possibilities, to remove advertisements in web pages or rewrite client requests based on their given URL or URI. This chapter details how they work, from a protocol level, and provides example configuration settings such as sending only specific users through the redirector or conversely, letting specific users bypass the redirector altogether.

Squid can be configured to use various user authentication methods to allow or deny access. Chapter Twelve, Authentication Helpers, covers these options. Squid can talk HTTP Basic, HTTP Digest and NTLM. Each type is well explained in how it works and detailed in how to setup.

Chapter Thirteen and Fourteen fully explain logging and monitoring. The logging chapter explains the type of information each log file catches, a full description of each error or information type (which is a great reference that I made full use of) and configuration directives that change what is logged or how it is logged. Monitoring Squid covers the Squid Cache Manger (A web front-end to many great statistics), a brief mention of using Squid-RRD and using SNMP. Such monitoring statistics include, file descriptor allocation, byte hit ratios, cache hits and cache misses and a wealth of other useful information.

Chapter Fifteen, Server Accelerator Mode, explains Server Accelerator Mode, which is also known as Surrogate Mode. It is a neat trick where Squid stills runs as a proxy, however, the Squid server is proxying the world (or a select few) to your server. One obvious advantage includes performance (or Slashdot hardening if you will). There are several config directives explained here as well as some gotchas.

Chapter Sixteen, Debugging, is the is one of the few chapters that I did not need to reference. Although, if you need to, there is some good information provided.

Appendix A comes with a config file reference that actually provides more information then the comments in the configuration file (Holy moley!...they better trademark that idea before other authors catch on!).

Appendix B briefly covers memory caching and optimization.

Appendix C shows how to use delay pools to limit user bandwidth.

Appendix D details file system performance benchmarks to show you filesystem and operating system differences.

Appendix E discusses running Squid on Windows using Cygwin.

Appendix F covers auto configuration of Squid clients to avoid needing to physically visit the many machines you administer.

In conclusion:

Pros: This is "The Book" for Squid. No skipping from chapter to chapter, the author was also the designer and still one of the maintainers, fuller descriptions of the configuration file directives that the configuration file comments. It is a great reference.

Cons: Really the only thing that I didn't like was that he only discussed HTTP proxying. There is a brief mention of FTP and SMTP, but only a couple of sentences. To be fair, in the preface he did mention that he would would of liked to written on these topics but didn't have time.

For the new comer I recommend to buy this book if your finding an alternative for Microsoft box like ISA or MSProxy 2.0.

Squid is robost and a very stable Proxy Server, you can use it even in Entreprise consumption..trust me I use it since 2001.

If your looking for technical books or documents about Squid, this is the one your looking for...

Back in 1998 when I was running my own ISP, Squid was a lifesaver because it allowed me to provide excellent web response to customers over a very modest upstream connection.

When I moved on to consulting Squid was the answer to a wide variety of client problems from employee Internet access control (Redirectors) to company website performance (Server Accelerator Mode) to plain old web page load times (Proxy Cache).

Now that I've moved in-house in a large corporation (30,000+ employees) and I've found out what commercial vendors are charging for their solutions to each of these problems, I have gladly used my knowledge of Squid to save us money.

Of course, that knowledge was not easily won, at least not for me. Because Squid was an open source project there was a lot of information available on the Web, but, of course, because Squid was an open source project, it was hard to find a definitive answer to my particular problem without asking a lot of dumb questions on newsgroups or making a lot of trial and error attempts tweaking compile time options, system changes and configuration file settings.

I have waited for this book for a long time.

I was concerned that it might be too detailed to be readable. Thankfully, Duane Wessels, the primary architect of Squid , has laid out this book to provide simple access at the Macro level. The chapter arrangement and organization are very intuitive. And yet the book still contains enough information to satisfy almost every question.

The one caveat I would make to a reader is to maintain situational awareness while delving into a chapter because, without noticing it, you can suddenly be confronted with pages and pages of configuration file details. There's no avoiding it, when a book says `Definitive Guide' on the cover you expect to have full coverage. It's just that the book is so lucidly written that the transition from high-level discussions to detailed facts might catch you un-aware.

And, really, it's that kind of feeling that lets you know that you're reading a very valuable text. I spent the first hour after I got this book skimming each chapter, happy at each additional topic I discovered. Then I went back and asked it the two hardest questions I have faced using Squid over the past year, in each case the answer was easily found and fully explained (Mr. Wessels deserves an award for making transparent proxying understandable).

The wait for this book was well worth it. I highly recommend it to any person working with, or thinking about working with, Squid.

This guide will pay for itself many times over. If you are considering a caching server for home, office or business you need this book.

My previous experience with proxies was MS proxy server 2.0 and I was a little apprehensive of this project; not to worry. Forty six pages into the book, squid was running; total time invested including installation of the program was about 2 hrs.

Another two hours of reading and precious few changes to config files and my log files are rotating, all ports I need exposed are open and the rest are hidden. I have already been able to tune squid to accelerate delivery of content using *only* this book as a guide. I haven't even had to look at the online documentation for squid (the first time I ever recall that happening).

Not only is my internet connection now available to all users, but also every one is browsing faster than they were before on single dedicated dial ups.

I can't say enough good things about the book or the program. In 14 years of networking I have seen the good, the bad and the ugly. This is one of those rare guides whose author is extremely knowlegable and the material presentation is flawless. I have a large computer science library and in my experience, it doesn't get any better than this.

Bravo Mr. Wessels!

I stumbled upon this book at a CompUSA and have found it to be one of the the best basic but thorough overviews of OS X 10.2.x. I needed a book to give my users new to OS X. I wanted something to help them get used to the new inteface and features but I didn't want them overwhelmed by too much detail. This book fit perfectly. It uses text and illustrations very well and describes things clearly. Everyone who has used this book has gotten up to speed quickly and with little help from me. That's success!

I bought my 'new', used ibook on ebay and so have no manual. The guy was nice enough to send it with Jaguar installed though, so I popped over to amazon, and bought this little guide. I am up and running, with an updated ISP, browser (safari, free at apple), and cooking along with icons making sense and configurations configured, ALL because of this little book! Now I know I have to get one of those big heavy books for the Big Stuff, but I am good to go in the meantime.

I am a recent convert from the 'PC' world to the MAC world. I was looking for a book to get me into the MAC quickly and easily. I am very computer literate on the 'PC' but needed the translation into the Apple world. A friend of mine has praised Greg Simsic's books on Photoshop, so I knew this would probably be a good book to consider. I have been very happy with it. It is concise and clear and seems to point out all the things I need to know to become comfortable with the MAC. It is slim enough I can keep it in the bag with my G4 laptop-always ready for quick reference. There is a very thorough index and table of contents to get you to what you need to know. And the information is clear and to the point. It seems to cover all of the basic information for me to get around the OSX system and its applications. I cannot believe the reasonable price on this book. I don't think I have ever bought a computer book [this price]. What a bargain this book is ...

I've been using Mac computers for more than a decade, but I have to confess my first bootup of OSX was a jarring experience. Where'd my control panels go? What's the dock? Where are my files? For the first time ever, I decided to go out and buy a guidebook to a Macintosh product.

Which brought me to this guide to OS X Jaguar conducted by friendly natives Greg Simsic and Katy Bodenmiller. The entire Simsic/Bodenmiller series is a tonic for anyone who resents the condescension of that "For Dummies" series and its ilk; rather than treating its reader like a slow third-grader, Simsic and Bodenmiller get down to business without all the superciliousness that keeps all self-respecting Mac users far away from those little black and yellow Cliff-Note's-like books. At last, a software guide I don't have to be embarrassed to read in public.

With its learned, front-porch and down-home idiom, Start! takes the reader from startup to moviemaking with savvy tips for everything in between. The layout of the book is as clean, logical, and as easy to navigate as OSX itself. Perhaps the greatest achievement of this book is that Simsic and Bodenmiller are able to address two very different audiences-the die-hard Mac devotee just making the switch from OS9, as well as the newly PC-cured-without wasting the time of either. If Jaguar makes you pine for nine, get this book. You'll never look back.

Greg Simsic and Katy Bodenmiller have written the PERFECT beginner's guide to Mac OSX. I teach OSX classes to new Macintosh users (univ. faculty) and I've gone thru lots of OSX books and materials. This is by far the best I've seen. Simple, straightforward, immediately to-the-point. It's written with a clarity and understanding of new users that is hard to find in many of the intro-level books. Greg's books have always been among my favorites, and this ranks with the best.

Trying to learn useful things about XML can be hard. XML is so flexible and can be used for so many things, descriptions of it have a bad tendency to be vague, never touching the real world. Or they are too detailed and technical to easily understand. This book has a really nice balance of these factors. For example, if you want to know what a web service is, and want to see an actual example of one without an overwhelming amount of technical detail, this book is a good place to look. You can see the code and what's actually needed to implement it.

As a strategic decision maker in the software development industry, transitioning into XML based technologies is at the top of my priority list. Strategic XML provides a very good introductory through advanced study of the topic. The author not only educates the reader from an academic perspective, but goes in depth with real world examples. He actually goes one step further and points the reader toward suitable tools and development platforms. For anybody moving into (or already in the midst of) joining the XML world, I would highly recommend giving Strategic XML a read.

I love this book, it's not your average learn to build a CD or Book database in XML. If you want to learn the XML, buy a generic fat red book with the lots of faces on it, if you want to learn how to apply the XML to practical situations, get this one. It's not going to take you years to read and the selection of applicable quotes at the start of each make it quite amusing and exciting. Add a bit of method to your madness, buy this book and apply a Software Engineer's approach to your data modelling.

I really liked this book. It gave me some very good insight into how to use the XML I have been learning for the past 2 years. It is not filled with a lot of useless rehash of XML primer material, it has a real nice review/overview of the technology and then focuses on the real issue of how to use it to solve business problems. I would highly recommend this book to anyone who doesn't need a 600 page regurgitation of XML basics, but instead is focused on solving problems with an exciting technology!

I initially read this book because I know the author and I promised him I would. I'm not a programmer but I am responsible for the technical direction of my company. Suprisingly, the book was written in plain enough English to give me a good general understanding of how to use XML, SOAP, Web Services etc. I'm passing it on to my programming department as a primer to start getting us up speed on these technologies.