Software Books

We've had this book for a long time and we still bring it out every now and then.
I think we enjoy the nostalgia of reading a favorite book together and we still
like seeing Marvin's adventures in the city and trying to remember where the
emu and the cat are. It took us years actually to find the emu on the subway.

This is an awesome book. I used it with fourth graders to teach the organization trait in the 6 traits writing. The kids loved the story and suggested we write a spin off of the book. They did an awesome job and made their stories into books and illustrated them. Highly recommend it to get students motivated to write.

I had never heard of this book before my son received it as a gift. He was about 9 months old and would insist that we read it again and again. He is now 4.5 and still likes it. And his little brother has enjoyed it just as much. The illustrations are fantastic and its fun to search for Marvin on every page. I highly recommend this book. I also love the language - it uses fantastic, descriptive words. My soon was 2 and used the words mesmorized and exhilarating because he learned them from this book.

My preschoolers love this book, not just because of the vivid illustrations that go with an easy-to-follow text - they love locating the hidden ostrich, police officers, and black cat tucked into nearly every single page. Check out the clouds...they look like fish, dinosaurs! Can you find Santa Claus hidden in Yankee Stadium's crowd of thousands?

I confess - my husband and I love finding the hidden pictures, too. Its also our favorite birthday gift for my kids friends. Get the book and scan the illustrations closely! Fun!

My three-year-old son enjoys this book so much because it lends itself to active participation. It is fun for him to spot Marvin, the escaped ape, in various settings ranging from a subway train to a ballgame to a ledge on a building. He also enjoys finding the two policemen who look for Marvin as he moves from locale to locale. I don't mind re-reading this book because of the clever illustrations and appealing New York City backdrops. And after reading the book for the first time, we have make a joke of finding Marvin--I say "Where's Marvin?" and he'll jokingly point to other animals or objects. His enjoyment of this book won't last forever, but it's been providing amusement for a few weeks now.

I couldn't put this book down until I finished it. Kerry does a great job of taking the reader behind the scenes at Fox.

It looks like I'm one of the few reviewers that didn't work for Fox Software. However, I have used and developed in FoxPro a lot over the last 15 years. It's still the best RAD tool that you can buy despite its treatment by Microsoft.

I thoroughly enjoyed this book and I think that anyone who has worked in software or worked for complete butthead would also like it and relate. It's so well written that I just wish it were longer.

Recently, I read Mr. Nietz's book while on vacation and found it to be very interesting and hard to put down. Within a couple of days I was finished with the book. This book is for all audiences and you don't need a degree in computers to enjoy it. I highly recommend this book and I look forward to reading other books by Kerry in the future.

Once I began this extraordinary book, I could not put it down. It's a page turner with a story that will appeal to all readers. I worked at Fox Software with Kerry for over 4 years. This story of Kerry's experience at Fox Software is a wonderful reminder that how you get to the top is more important than how high you get.

There have been many stories of what the inside of the high-tech business looks like from the most famous and successful business leaders. Most of these stories are attempts to write history and promote themselves. This story is about a hard working and honest guy who wants to work hard and make something of himself by joining a small software company. After reading this book you can tell that Kerry wrote this book to just share his experience. He is not trying to promote himself, and by doing so he tells a story that so many people can relate to, and he records for all of us a fascinating story of a small software company at a time when the industry was growing exponentially.

This story has a happy ending, despite all of the obstacles presented in the book, Kerry and others continued to work hard and were rewarded years later at Microsoft. I am looking forward to more great books from Kerry.

FoxTales is an excellent read. Once I got started, I simply could not put it down. As an employee that actually worked in the offices of Fox Software, I always felt that Fox Software was a company that succeeded more in spite of its uppermost management, rather than because of it. At times Fox was an exciting and awesome place to work and at others, it was humiliating and torturous. Kerry does a great job of presenting the experience as a whole and of wrapping up a series of somewhat loosely related events into a very entertaining story. It's nice to see someone tell the outside world what it was like at Fox Software.

If nothing else, Dr. Fulton had an excellent eye for talented developers and he certainly did manage to assemble an incredible team. It's great to see how Keary and others were eventually rewarded by Microsoft for their efforts and perseverance.

I had to cross through several WCF books before finding the right one for me. This book has very easy learning approach - going straight to the technical WCF matter. In a good intro chapter, explaining everything about creating and configuring WCF servers and clients the book defines serialization, hosting, bindings, behaviors and other specific WCF basis. All these meanings are discussed deeper in consecutive chapters.

Not only does the author write well and explain concepts expertly, but from the effort she expended in putting together the instructional materials that readers can download to follow her along for the "hands on" parts of the book, one could tell she understands very well what readers need from a tech book writer!!

I was looking for a good book on WCF and saw that this book received great reviews. I started out with their other book "Programming WCF Services" and thought maybe this one would be better to start out with. I am now returning both of them and will try either the Pro WCF: Practical Microsoft SOA Implementation (Pro) book by APRESS or the Professional WCF Programming: .NET Development with the Windows Communication Foundation (Programmer to Programmer) book.

I personally don't like the way this book is organized. You walk through several examples in the first chapter using terms and technologies that you haven't learned about yet - I found myself jumping around in the book to try to figure out what I just typed into Visual Studio and why I typed it. I like to learn a little bit about the concepts before I start getting into the examples.

I am very happy with this book: it's easy to read, the structure is very intuitive and logical, and everything you need to know is covered. If you're just starting with WCF and you're looking for an excellent resource on the subject, look no further.

I purchased this and Lowy's book on WCF. Of the two, I'd say this is the one that will make WCF real to blue collar developers. More technical books need to be written this way. The author does an outstanding job of describing the pieces and parts of WCF from a functional standpoint before leading the reader through simple step-by-step exercises. These do a solid job of reinforcing the theory. I normally blow off working through sample code in technical works, but with WCF, it really helps to explore some of the nuances to things like serialization, callbacks and security. These are best appreciated by doing hands-on walkthroughs and fortunately, the author has provided very good examples in the companion download.

Lowy's book is good for different reasons, but I feel far more conversant in the WCF area having read and re-read Bustamente's book. Lowy's is a nice companion and it goes deep into stuff that, unless your current project really needs it, you'll brain dump in two weeks. Quote Lowy at swank cocktail parties with the hoi poloi, but use this book when you want to gain a solid understanding of this thing we call WCF.

Bustamente writes clearly and to the point. Git r' done types like me who are interested in exploring the functional without getting lost in the minutiae will appreciate Learning WCF.

This book is not about SOA although the author does touch on some basic premises governing what it does for the enterprise. Unlike Lowy, there weren't any real groaners about how SOA is going to replace OO and end world poverty. OO maybe got 30% penetration among software developers in formal polls. (As an informal measure, go into any MS shop and check out how many OO diagrams are created by devs in their work and you'll see what I mean. Most MS shops won't even spend money on third party modeling tools.) SOA isn't going to do any better and it addresses a different set of problems than does OO. Bustamente gives developers a solid grounding in appreciating what WCF can do while leaving all the fluff about "paradigm shifts" and what-not for others.

I've worked in the telecom industry for years, and this dictionary accurately defines more telecom terms than any other. However, it is not very well-written. The style is really colloquial and inconsistent. One definition may read like it's straight out of IEEE-100, while others sound like a hallway conversation between engineers. Even within a definition, the same term may be capitalized in one instance but not in others. So, I'd put it in the library for sure, but get The Authoritative Dictionary of IEEE Standards Terms (IEEE 100), Seventh Edition and McGraw-Hill Dictionary of Scientific and Technical Terms, too!!

This book is perfect for computer enthusiasts, business owners who utilize computers and telecommunications, scientists, a wide
constituency of educators, computer programmers, web designers and just about anyone who may need to understand computerese in simple English. Important definitions are listed; such as, ADCU, back lobe, card cage, isochronous distortion, etc. There are strategies to minimize calling charges by utilizing prepaid cards for national and international calls. Important computer user groups may be accessed at:
o atmforum.com
o ectaportal.com
o ecma.ch
o gigabiethernet.org
o 10gea.org
o 3GPP.org
o aitp.org
o ansi.org
o apcointl.org

The book is a solid investment for any computer professional, teacher, computer user group or business person.

I use this book all the time. This is the perfect reference book for every engineer working in the Telecomm field

Less than nine months ago I started working for a software company that makes OSS/BSS solutions for Telecommunication operators.
As an economist I had a lot of problems understanding the sector and the acronyms that telecommunication people love to use. Having this dictionary at hand did definitively help me a lot. I do recommend it to every person wanting to get a general understanding of the sector. Only a pity that Harry did not include more graphics to help with the explanations.

As a telecommunications student, I was leery of all the abbreviations and unfamiliar terms. This book was very helpful in explaining new words and phrases, especially since the telecommunications industry is full of strange acronyms. Very worthwhile!

I already read many Oracle books from Oracle Press & other publications. They are very good. This book takes different approch of How-to Style content which is very much practical & solves day to day administrative needs. Topics are covered in detail. Most importantly examples given are from grounds up. Excellent! This book is also helpfull for all who know a little bit of Oracle Database & want to know more in depth

We all know, especially here in Brazil, the money that one pays to have a good Oracle trainning. If you already have a little knowledge of Oracle and its jargon and are self estimulated, this book will take you to high level of expertise without a pain . Want to know Oracle ? Start with it.

Among all the Oracle reference books, I found this one to be the most useful and practical book. This book is very well written and has an easy to read format. The detailed step-by-step instructions in Q&A section helped me solve problems quickly. This saved me much time and effort than going through piles of other reference books and trying to pull pieces of information here and there together to get a complete picture. I highly recommend this book to Oracle DBA's in all levels.

As an Oracle Instructor and DBA I've had the opportunity to review numerous Oracle texts for DBA's and have to say I've been quite disappointed with most of them. Mr. Yuhanna's book however is an exception. Out of the many DBA texts I have on my shelf this is the one I goto most frequently. Unlike other texts which spend excessive amounts of time covering uncommonly used features and little to no time covering commonly used features this books covers almost all the basics in a hands on approach. The book is setup in a step by step how-to format. Although it doesn't discuss concepts much that is not its purpose and the best concepts book is the Oracle Documentation anyway. I've have yet to see a good how-to DBA book until I came across this one. As a consultant/instructor I recommend it quite frequently.

The book is very useful for both new and experienced DBAs because it has a lot of practical examples. I especially like its Q&A format with scripts which makes reading very interesting.

I've read quite a few of Jim's works over the years, and he has never failed to impress me. This book should be required reading for any project manager!

My initial pre-read perception of this book was that it was going to be just another perspective of agile methods. I was wrong. Coplien and Harrison have dissected development teams to identify the key criteria leading to successful efforts and high-performing teams. Beyond process, this book identifies the organizational structures required to make the processes work.

From an organizational perspective, roles and responsibilities within your development teams are a primary success criteria for your agile (or any other process) adoption. This book presents how and why key roles within your teams work and why teams without these key roles don't work. The way they have presented the material provides for a quick cross-reference when you are looking for solutions to help your teams.

Beyond the organization patterns themselves, I believe some of the richest material in this book is presented in the last few chapters as they present the history and importance of organizational structures, roles and responsibilities in applying process - "Process emerges from structure, and structure emerges from values". There is great value in this book beyond most software development process books.

As project managers, most of us who've been in the field working for a while come to realize that successful project teams are more the result of "good" ongoing social engineering of one sort or another rather than just dumping an almost randomly selected group of people together, coming up with an MS Project Plan and saying "do this" (the Death Star approach, all to common in large traditional process-driven IT shops). After this has happened to you, painfully, you begin to come to the realization that perhaps there's more to project management than the mechanistic "people are interchangeable resources" PMBOK-style approach.

If it hasn't already, it begins to dawn on you that the "soft" side of project management (client relationship building, communication within the team and between teams, team dynamics and team morale, motivation, empowerment, commitment, a human-style of project management) are as important or even more important than the technical work and the technical skills required. Most of us have run across teams with prima-donna's who think they're the cat's whiskers, be they project managers or technical personnel, who have the personal graces of a warthog and who are incredibly destructive to team morale and team performance. They continue to exist, sadly, and because they often deliver, albeit at the expense of everyone who works for them or with them, they continue to survive in "Death Star" style IT shops where delivery is all important and the style of successful delivery means nothing or is short-sightedly disregarded. OK, so that's my rant.

Now for the book. We've all seen successful projects and successful teams (or at least, I hope we all have). Some teams gell and perform way above the norm. What this book does is distil over 100 successfully applied organizational patterns of one sort or another from real projects in real software development groups. These patterns are broken down into logical groups (Project Management Patterns, Piecemeal Growth Patterns, Organizational Style Patterns & People and Code Patterns) which are dissected and explained, with examples provided. What the authors have done is to identify and describe key organizational patterns which are used by successful teams - not processes, but organizational structures of various types that are needed to make processes work successfully. A large amount of practical experience has gone into the content - over ten years of research experience from the authors alone.

I've read a lot of books on Agile, but this is the first I've come across that sets out organizational patterns - and does it so effectively that you'll wonder why all the stuff in here never occurred to you before. As you read through the book, you'll see patterns that will make sense, the kind of "ah-ha, that's what the problem is and this is how I can dom something about it" sense. You'll find this book useful in that the contents can be taken and applied right away. It's easy to pick what is most useful for your team, what can be applied immediately and what would be nice later on, once some of the basics are in place. The content is practical in that you can easily identify what your problems are and what pattern would help fix it, why the pattern is intended to fix it, and there's good advice on how to introduce new patterns.

With over 100 patterns, there are a lot, but they're set out concisely, a page or two to each pattern. There's no fluff, it's well-written, there's no appreciable bias, there's a lot of material, including some good coverage of the importance of effective organizational structures in applying process. As we all know, all the process in the world will not a great project team make. The book's structure is coherent and well-organized, the patterns described can be used individually or as groups and the authors give you some pretty good ideas as to what's immediately useful.

And the pictures all the way through the book are great! A nice humorous touch that helps make the point each time. Overall, I'd recommend this book very highly as a resource to anyone managing a project / team, whether Agile or not. There's a wealth of practical advice in here that any project manager could take and use, although the orientation is towards Agile Projects. An added bonus - unlike many technical books, this one won't date quickly - organizational patterns that work don't change much over the years, unlike programming languages. From a practical point of view, I've applied some of these patterns to teams I work with and the results have been positive - I've also shared the book with co-workers and they've all found it both illuminating and useful.

This book has to be The Grand Unifying Theory of Software with respect to managing the people and processes involved in software production.

To anyone who has worked in the software industry, this book is clearly the product of an enormous amount of practical experience in both management of people and projects as well as the development of software.

Coplien and Harrison have written a book which both the project manager and software engineer will understand and will immediately be able to apply to their respective work environments: This is because the book cunningly captures essential organisational concepts using a framework that is familiar to software engineers. Thus, the concepts will be by recognised by staff trained in business as well as those trained in software and systems.

I strongly feel that the material covered in this book can achieve a common communication basis between managers and engineers, and can help business developers understand the nature of their people and organisation.

If I could insist that all people in software read this book I would; but without the policing power, I can only highly recommend this book to those involved in all facets of software.

OK, I have to admit, this is the first book review I've ever written on Amazon and having read a lot of good books I should probably get off my a** and write more :-)

As a former developer and now a software development manager, I have come to realise that the "soft side" or sociology of software projects (communication with clients, communication with teammates, project management, team dynamics, cultural issues, morale, division of work, remote collaboration, etc) is considerably more complicated than the programming work itself.

Over time, you start to see patterns emerge such as "start a large project with a small experienced group and gradually phase people into a project as time goes on". This book does by far the best job of cataloguing and explaining dozens of these patterns related to (1) software project management (2) structuring, building and nurturing software project teams and (3) organization and division of development tasks to maximize the effectiveness of the team as a whole.

Highly recommended to anyone involved with software development at both the management level and in the trenches. Have fun!

Love this book! The pictures inside are just gorgeous and information about the camera settings for each picture are included. The book is an easy read and is full of insightful information. There are practice sessions at the end of each chaper too. I can't say that I have taken the time to do any yet, but the suggestions are still great none-the-less.

I highly recommend this book to any avid photographer and aspiring professional photographer. I'd like to get more books in the photoworkshop series.

I rarely take the time to write a review for something I buy. But this book has really touched me and enlightened me. It is so well written and organized. I am a mom of six and love taking pictures of my kids. I'm trying to learn more to be able to take really good pictures. This book was so straight-forward. The pictures are REAL - not the strange art-studio type pictures that seem so popular now. I really appreciate that the information is shown for each picture. It's really helped me "see" what differences aperture and shutter speed make. The exercises at the end of each chapter have pushed me to really think about what I'm taking pictures of and stretch my thinking a little more outside the box. I can't wait to complete some of the assignments and upload them to the website. I've bought 6 or 7 photography books on amazon and none compare to this one- its just the best and well worth the money. What I want to know is - does Ginny offer workshops? I would LOVE to attend one if she does!

I found this photography book to be informative and beautifully illustrated. One of my favorite pictures is of a new born. It shows only part of the head, a shoulder and curled little hands. We see no clothes or blanket,just soft baby skin. Photo Workshop is a good description. The chapters are complete enough to instill confidence to try the different techniques. The assignments at the end of each chapter are motivating. I would recommend this book to those who are trying to capture the spirit and innocence of children. These techniques also work in capturing a pets personality. I have given this book to each of the parents of my grandchildren,and am looking forward to receiving some great pictures.

The book was exactly what I was looking for. Help with the how to on the technical side,but was helpful on setting up shots. Looking around my house and seeing how the book would "shoot it" then applying it with my DSLR. Composition and Lighting was extremly helpful to me. This book was well worth my investment.

I've read this book from cover to cover. I love it. As a beginning photographer, this book was very helpful. Not a lot of technical info. Just enough guidance to get me going on my own.

Till I saw this book and Bert Monroys website my imagination and creativity for minimally very finite. Its amazing how he shows what can be done using image editors like photoshop. Its just blows you away. My wife thought the pictures in his books are photographs and when I told her bert monroy created them in photoshop, there was no sound from her. She was quite amazed. This book is well recommended. Authors like Bert Monroy truly amazes with their talent and give us additional thoughts and inspiration on how to improve our work.

I found this book very useful, very well illustrated, as Bert Monroy describes his technics. He teaches methods that opened my mind to the power that Photoshop CS has. While he covers many aspects of the program he dos not indulge in the usual rehash of every photoshop feature, focusing on specific projects. His reputation for a graphics artist and teacher are well deserved. Wonderful examples, just enough detail to convey the point without beating you over the head. Included color photos are well laid out, his teaching method couldn't be better. The tone will particular instruct the novice or intermeadiate user, but everyone will find something of use here. If you are looking for blow by blow 'how to' for every feature, look at Photoshop CS Sudio Techniques, or the Adobe Class Room in a Book. I only wish this book had more samples, examples. If you can't buy it, hope your local libray has or will. Do this for its artistic voice.

This book will get your imagination going. Some great tips.

The only reason I don't give it 5 stars is that there could have been more content.

Bert Monroy is probably one of the most talented Photoshop users there is. If you've ever seen him on TechTV, you've seen how effortlessly he uses PS.

This book is full of amazing artwork Bert has done with Photoshop, along with a lot of tips and techniques from the master himself. You'll have a hard time believe that this book isn't just a collection of photos. Bert style is so photo-realistic it's jaw-dropping.

Definitely a must-have book for any PS enthusiast. Even if you don't plan to use PS for Photoreal artwork, there are techniques here that are applicable to other uses for PS but the book itself is worth the price just for the awe factor of Monroy's work.

Bert is a great artist and teacher. I took a class from him, and learned so much, but couldn't absorb it all at once. This book allows you to learn his techniques at your own pace, and will give you the confidence to start creating images from scratch in Photoshop, or add painting techniques to your image manipulation. Highly recommended for intermediate to advanced Photoshop users and all artists.

Issues specific to Open Source are well-covered in this book. I found the section titled "Handling Difficult People" especially useful; his advice in this dodgy area is to act eloquent and keep feedback directed at the problem, not the person. If the person *is* the problem, nip in-public issues in the bud and contact the person directly to resolve the personal issue(s).

Fogel presents lots of down and dirty day-to-day details on how to create excellent software. Not just Open Source, either... the transparency built into the processes he describes are also useful within a company firewall.

Fogel places a huge emphasis on development by random unsalaried people, but I feel that most important and rapid development is due to corporate sponsorship.

Overall: excellent. Read it cover to cover, refer back to it often.

If you are thinking of starting/managing a project in an "open-source" model, this is the book you MUST read.

The book is very well written and goes over lessons learned of others that created their own open-source projects. Believe me... every step so you don't have to guess anything!

How to start, how to document, where to deploy the project, what people to invite, whether or not coding standards are necessary, democracy versus dictatorship, all of these questions are answered inside.

A friend of mine has told me that much of the information in this book can be seen for free in video in Google. It's worth looking for.

I read the book in 5 hours and i think my time was very well invested. I now believe that this model is not only suitable for small projects but to larger projects. The complexity of the system will not the an issue if you apply the rules in the book. I still have to try it though... ;-)

Just yesterday I was talking to a friend about this book and we discovered each other very glad with it. First of all, the author has a lot of experience with the theme in question. Furthermore, Karl Fogel is very compelling with words. He knows how to write down his experience in a way that is pleasant, certainly due to a lot of writes he had made through plenties of open source projects.

With this book you will be in touch with topics like the needed infra-structure to setup open source projects, the dinamics of the open source community, strategies for packaging and releasing software, common issues that arise in open source daily development and how to workaround then, a brief about licenses (with properly links for more information on this topic); just to highlight some aspects.

This book was the first hand someone land me into the open source world. It's helping me in three ways: to extract more from open source softwares that already exist, to start my own open source project, and to look at software development through a new, different, and till now better perspective.

Hope this review helps you!

If you have already read pretty much everything that there is to be read about why you'd want to start, manage, fund or participate in an Open Source project, but want to know everything about how best to do it, then Karl Fogel's Producing Open Source Software is the book for you.

Drawing from his extensive experience with the Subversion project, Fogel provides in this book a comprehensive overview of all aspects of Open Source software development, covering technical, social, political, economical, legal, and managerial aspects.

While the book is more aimed at medium-to-large scale projects, especially those involving some kind of corporate entity, there is much in it that is applicable to most projects, excluding maybe only those little, one-man efforts that rarely become successful. But if you are the originator of one of the latter and, should it suddenly attract a wide following, you'd better be prepared to face the unavoidable problems that popularity brings.This book will come in handy in this case.

Here are, in my opinion, the strong points of the book:

* Providing a concise, yet comprehensive, overview of all aspects of Open Source development. This is really the manual of open development.

* Demonstrating that there is much in open development that is similar to more traditional, corporate-style software development (you cannot always rely on good will and volunteers), but also much that is different, in motivation, rewards and objectives.

* Putting the accent on the human aspect of development: mutual respect between participants is often the deciding factor in determining whether a project will thrive or fail. Since even the best of intentions sometimes are not enough to foster a peaceful, productive and collaborative environment, Producing Open Source Software contains a lot of useful, practical advice that you can follow if you want to keep developers happy and motivated.

It's easy to make the mistake of viewing this book as "too fluffy" or perhaps too soft to be of any use to the practical user or developer of open source software. Nothing could be further from the truth: in a classic open source way, the author has compressed man-centuries of OS community experience into a practical working guide for anyone who wants to do something serious in this area.

If you want to understand programming the Flash Communication Server and it's capabilities this is a good place to start.

Although I'm using Flash Media Server 2, this book is still highly relevant as not much has changed. The core objects and language is the same so I would not hesitate to recommend it for anyone looking to use FMS.

This book is all about the design of applications using Macromedia's Flash Communication Server MX. FCS MX enables the building of media-rich web applications by taking care of the basic tasks required in the networking of the applications. Thus, you can focus on the application itself rather than worrying about low-level communication details.

Since this book is concerned with situations where multiple Flash applications will be executing on the same server simultaneously, there is going to be considerable effort involved in coordinating events, which is addressed by this book. You should already have FCS installed and running on your server and you should also have Flash MX available on the client. The following is description of the book by chapter:

Chapter 1, Introducing the Flash Communication Server - Acts as an introduction to FCS and an overview of the whole book.

Chapter 2, Communication Components - How the FlashCom communication components encapsulate commonly needed features such as chat, video recording and playback, bandwidth control,and user configuration. These components implement many basic building blocks for your application.

Chapter 3, Managing Connections - This chapter covers connections in more depth past the SimpleConnect component, including how to write custom code to handle various changes in the connection status as well as different errors.

Chapter 4, Applications, Instances, and Server-Side ActionScript - This chapter describes how to write Server-Side ActionScript and work with the objects that control application instances and the Flash movies that connect to them.

Chapter 5, Managing Streams - Offers a somewhat oversimplified but complete example that shows the basic steps in publishing one live stream and subscribing to a second.

Chapter 6, Camera and Microphone - This chapter explains how to use both the Microphone and Camera classes to record live streams. These classes are at the heart of most communication applications involving multimedia.

Chapter 7, Media Preparation and Delivery - This chapter covers many details for compressing and streaming audio and video.

Chapter 8, Shared Objects - This chapter starts an entirely new subject - shared objects, which provide a mechanism for the transmission of data between client and server.

Chapter 9, Remote Methods - This chapter also shows how to broadcast method calls to every movie and application instance connected to a shared object or stream, or send them to and from individual movies using RMI.

Chapter 10, Server Management API - Discusses the Server Management API and its applications, including monitoring a FlashCom Server, gathering statistics on application instances, and managing the log streams.

Chapter 11, Flash Remoting - Demonstrates how Flash Remoting can be used to add data connectivity to FlashCom applications. Flash Remoting can access web services, server-side scripts, CGI applications, XML files, or the local filesystem with the help of an application server such as ColdFusion.

Chapter 12, ColdFusion MX and FlashCom - Teaches some specifics involved in using Flash Remoting with ColdFusion MX and FlashCom. There are some practical working examples shown that demonstrate how you can leverage the benefits of Flash Remoting in conjunction with FlashCom.

Chapter 13, Building Communication Components - This is the first step in building complete applications, and is demonstrated through an extensive example.

Chapter 14, Understanding the Macromedia Component Framework - How to modify an existing component and how to create a new one. Also discusses server-side framework code and its core features and data structures.

Chapter 15, Application Design Patterns and Best Practices - Describes some of the best practices available to application developers. This chapter provides some useful design options, patterns, and best practices that will help you build better applications.

Chapter 16, Building Scalable Applications - Deals with building multi-instance and multiserver applications that don't bog down as the number of client connections increases.

Chapter 17, Network Performance, Latency, Concurrency - Traditional network design issues affect FCS also.

Chapter 18, Securing Applications - Specifically this chapter examines the three A's of security - Authentication, Authorization, and Accounting.

Excellent book, stuffed of examples very well explained, easy to read and to understand, essential for who desires initiate or even though to profound itself studies on FlashCom.
Obligator reference in projects involving FlashCom, either for fast consultations and advanced tasks.
Excellent approach of subjects as Design patterns and security, yonder a perfect demonstration about audio, video and much more.

If you're a developer looking into real-time server communication using Adobe Flash, this book is a must-have. It guides you thru various levels of application development in an easy to understand format, and provides well documented pieces of code to assist you in the learning process of putting together your project:

Topics covered include:

- learning about components and how to use them
- establishing and managing client connections
- publishing live and recorded streams
- local communication with clients
- remote communication with outside applications

The book also shows how to build and integrate your own custom components, and how to scale your application using the components that you've created. Other highlights include information on how to use shared objects and server management API, as well as ways to improve both design and performance.