Computing Internet Books

This book is the best resource for Exchange development, written by the developers who work on Exchange Web Services (EWS) this book is a must-have for any developer that is thinking about writing applications against Exchange. I can't recommend it enough for the examples, in depth explanations, and entertaining writing :)

This book is a must for all developers that want to benefit from the new Exchange Web Services protocols. MSDN documentation is not that great, but the book explains the internals, data types and procedures, giving clear examples. You can't go wrong with it, especially when developing using .NET

This book is not only powerful, but is a must have for anyone developing against Exchange Server either now or in the future. The explanations are both thorough as well as detailed and make it easy for those who have never written web services to get started. The examples are fantastic and complete and in no time at all I was able to get started. I would recommend this book to anyone, new programmers or experienced. Fantastic book!

Overall, I think this is a quality title. I just came here to warn buyers of a few things:
(1) There are many errors in this book. If you buy it, you MUST download the Errata document from ciscopress.com. Otherwise you will be confused. (2) This is the only book that I bought to prepare for this exam, so I have nothing to compare against, but I believe that some parts of this book could have been written much better, and other parts are unneeded. This book could be 50 pages shorter without the all the unnecessary "the following section will show you how to... blah blah blah" text. That's what the index is for! (3) This book does not progress in a very organized manner. If you are just starting, and you want something that you can read in a linear fashion, I might suggest looking for a different book.

This is an awesome book. Mr. Odom explains everything in a very simple approach. Leaving you with a good understanding of the material. The appendices are very helpful and the included Boson test engine finishes your preparation for the test. Although there were several errors on the Boson test engine but I cannot complain: The test engine is a freebie and the book teaches well enough to recognize these mistakes. Buy this book, for the main reason that it is written by one of the first CCIEs and knows his craft. Most other books are not written by CCIEs. This is important to me. Great job Mr. Odom.

This book does not prepare you for the CCENT Exam! This book gives potential test takers a false sense of security. The questions in the book and on the CD are extremely easy compared to the actual exam. Also the subnetting chapter is very convoluted not to mention the errata throughout the book. Buyers beware...

This book continues Wendell Odom's dominance in the Cisco Certification study materials market. Odom has consistently produced high-quality materials that do a fantastic job of covering almost all of the aspects of the CCNA exam(s). In this second edition of the materials, video training is included on a well-produced DVD. The subnetting lessons contained on the DVD are top-notch.

The book does a great job of covering the material on the new Cisco Certified Entry Networking Technician (CCENT) exam. The book covers networking fundamentals, LAN switching, IP routing, and Wide Area Networks. As with most other Cisco Press certification books, the chapters are organized in the following manner: the "Do I know this already" section, foundation topics, and exam preparation tasks. The "Do I know this already" section enables the reader to skip ahead in the materials if they feel that they already have an understanding of the topic.

There is a second CD included with the book that is very helpful. It contains Cisco Press support, the complete book in PDF format, practice exams, and a super-cool binary game! From my experience as a teacher in the Cisco Networking Academy program, I can tell you that binary and subnetting are two of the toughest topics for most students, and the material in this CD alone is well worth the price of the book!

I bought this book right before taking Cisco CCNA training. This book is identical to the material they give you in the ICND1 course. The benefit of taking the class is that a good instructor will give you additional information above and beyond what's in the material including do's and don'ts. Also, you have lab material that you have to do which is not available in the book. Be aware, however, that the material taught in the CCNA course (and thus this book) may not cover 100% of what's on the exam. That's because Cisco does not allow the people that write the exam and the people that write the study material to collaborate!! This means that even if you take the class you'll want to pick up other CCNA material such as exam cram guides, flashcards, and/or network simulation software. I haven't take the exam yet but I'm told Cisco has made the 640-822 exam even more difficult in order to make the CCNA a better regarded certification and have introduced a lower-level CCENT certification for Entry-level people.

If you're a .Net programmer, you might think an overview book like this is beneath you - it probably sounds like management oriented fluff. However, we all have to admit .Net is huge and constantly changing. It's tough to keep up on all its facets, let alone, put them into some sort of historical context. This book does that for you. What's more, it explains the why's and what-for's behind the various .Net pieces better than any other book I've run across. I think even experienced dotnetters will enjoy quite a few 'ah ha' moments reading this book.

If you're a management type, the first chapter alone is gold. Read it, learn it, and you'll probably be able to understand what your average dotnet programmer is saying. Best of all, when they call the Intermediate Language "bytecode" (which I've noticed happens pretty often) you get to correct them: "bytecode is Java - in dotnet we call it IL." Surely this moment of triumph alone is worth the price of the book.

One criticism: Why a lion on the cover? I think it makes this book look like one of those learn how to program X in 30 days books, that is, a cheap poorly written ripoff. This book deserves better! I'd put it in the same class as a great introductory text book, so why not make it look like one.

I'm a software engineer who has a background with C++ and Java. I normally stick up my nose at anything Microsoft. So I was skeptical picking up this book, but I'm glad I did. It presents the user with an overall look at the .NET framework.

This book is good for people with a Java background.

It probably wouldn't be a good book for the avid .NET user.

Excellent coverage - I learnt a lot and the examples are very good as well.

While this book is well written and provides an overview, it is important to note that there is absolutely no tutorial. If you are expecting an instructional section that is set up as a series of steps that progress through levels of difficulty and understanding that provide a working knowlege of the subject (as is implied by the word tutorial in the title)you will not find that in this book.

Good overview of the .NET technology. Although it is a bit out of date...

Actually implementing a content management solution, even for a small company, is a daunting prospect. Not only do you have to consider a myriad of concrete tasks in order to audit, centralize, and reuse your information. You also have to "sell" a major work-style change to numerous players. Even knowing where to start can be overwhelming, and that's where Ann Rockley's book Managing Enterprise Content comes in.

Authoritative and experienced, Rockley acknowledges that enterprise content management is not for everyone (a refreshing change from those pushing cookie-cutter solutions). In cases where content management could solve business problems, Rockley makes her case with calm conviction, breaking the subject down into logical chunks. In particular, her chapters on designing metadata (the "information about information" that is key to effective and scalable content management) and workflow (the designation of who does what, when) are lucid and comprehensive.

Whether your objective is to get a grasp of the subject, sell an implementation to your organization, or just digest what an impending implementation will mean to you, you'll want Rockley's book on your desk.

I came to this book from a very different direction than many (all?) of the other reviewers. I'm a technical writer ("content developer") researching methods and tools for single-sourcing technical documentation. For my purposes, this book was an excellent starting point in recognizing and understanding the considerations that must be taken into account when migrating to a single-source solution (i.e., one tool and set of practices for developing documentation to be delivered in multiple media), defining a new set of practices, and evaluating an authoring tool. I recommend this book strongly to any tech writer/manager who needs help understanding the basics of single-sourcing.

This book's title has probably attracted those interested in Enterprise Content Management. ECM has increasingly become a major buzz in business strategy circles as the information age tidal wave spills over into organizations and floods them with content. We're literally drowning. "Managing Enterprise Content" does not discuss ECM in broad terms, such as structured and unstructured content, email, scanned documents, OCR, ICR, etc. Instead, it focuses on content reuse. To take a simple example, a product brochure, a website, and a press release all include descriptions of a product. Why, the book argues, rewrite that description three separate times for each medium? Why not write it just once, store it in a content management system, and then reuse it over and over again? "Content Modularization" or "Content Reuse" probably describe the goals of this book less confusingly than "Managing Enterprise Content." But, in fairness to the authors, the current title isn't inaccurate, it just lends itself easily to misunderstanding. To reiterate: those looking for a course in Enterprise Content Management conforming to the Association for Information and Image Management's (AIIM) guidelines should look elsewhere.

Nonetheless, those looking for a strategy to manage distributable content throughout an organization should take a look at "Managing Enterprise Content." The focus remains on implementing a "unified content strategy," which translates essentially to an efficient reuse of content. Here the word "content" has a specific sense relating to verbiage authored for a specific use. Product descriptions, mission and vision statements, disclaimers, compliance and regulatory announcements, anything widely distributable qualifies. How does one efficiently manage the creation and the evolution of such content across an organization? This obviously implies some form of centralization (although this pregnant term gets strategically avoided for obvious reasons). And this further implies a software system. But prior to purchasing an expensive application, the business must align itself process-wise to enable content reuse. Otherwise the costly program will sit and rot. The first three parts of the book (I - III), comprising its first twelve chapters, discuss these necessary preparations and walk the reader through to implementation. This progression mirrors, for good reasons, the project management and software development life cycle processes. First, determine the concept or the "why?" of the project (Chapters 1 & 2). Then perform cost benefit analysis (Chapter 3 discusses ROI for content reuse), analyze and prioritize the current content infrastructure, the "As-Is" (Chapters 4 through 6), look to the future by modeling and designing the elements of the system the "To-Be" (Chapters 7 through 11), and finally implement the reusable content infrastructure (Chapter 12). Evaluation of software tools and technology should come before implementation, but the book instead covers these topics in Part IV (Chapters 13 to 18). So it's that easy to implement a unified content strategy? Well, no, not really.

Part V, the book's final section, outlines the inevitable issues that face organizational restructuring. Implementation of a unified content strategy will probably necessitate fundamental changes. Roles will get changes, people moved around, departments will get realigned or reorganized. All of this can sap morale or cause anxiety amongst employees. The author is not an authority on such issues, so this section of the book remains somewhat cursory and high-level. Conflict management gets deferred to a website (the book contains an out of date URL, but the book's website[...] has an updated address), and the advice presented here will probably not surprise anyone. Still, managing change remains an important part of any new implementation and this section, though rudimentary, will at least raise awareness.

Lastly, the appendices contain a grab bag of information. Appendix C, on vendors, has probably suffered from age (these days, a lot can happen in three years), but it may provide some good leads. Appendix B, "Writing for Multiple Media," probably could have appeared in the main body of the book; it contains important details not covered elsewhere.

Overall, the book does give a plausible outline for implementing the proposed strategy. Some of the chapters may seem overly simplistic or overlong to those experienced with system implementations or business process management. At the very least, "Managing Enterprise Content" may introduce some readers to the concept of enterprise content reuse. That concept remains a challenging one that will likely mean different things to different organizations. So this book does not provide the final word on the subject, nor does it intend to. An organization can only use this book as a blueprint or a guidepost for implementing its own unified content strategy.

This book is an absolute must for Content Management projects. It touches all of the important aspects: Technical, functional and process. There is something for all stakeholders in a EMS/CMS project.

Especially good about this book is that the parts that are not your direct job are still very readable, understandable and interesting. It provides valuable insights in other peoples jobs and reasoning.

Coming from the technical side and with a lot of experience in setting up systems and also information architecture and DTD design, for me this book contained several new insights and some very helpfull checklists.

I am in the middel of a CMS project now, but I wish I had read it sooner.

Are you overwhelmed with the need to create more content, faster, customized for more customers, and for more media than ever before? Do you consider storing documentation on a server as an effective a content management system? Do you want to learn how content management will empower your organization? The answer to these questions and many more is covered in Managing Enterprise Content: A Unified Content Strategy by Ann Rockley with Pamela Kostur and Steve Manning of The Rockley Group. The Rockley Group is one of the leading providers of content management methodologies.

Managing Enterprise Content provides concepts, strategies, guidelines, processes, and technical options that will prepare you to meet the increasing demands of creating, managing, and distributing content. It describes techniques that will help you define your content management requirements, build your vision, design your content architecture, select tools, and overcome obstacles of managing enterprise content. It will help you to visualize the spectrum of enterprise content, the requirements for effectively creating, managing, and delivering content, and the value of developing a content strategy for your organization. That¡¦s a lot of information for one person to understand. That¡¦s why the book is written for three audiences: content managers, information architects, and authors. Managing Enterprise Content follows the same methodical approach that Rockley uses to teach content management in seminars and workshops.

I was expecting the book to jump into the technologies to implement a content management system. But that¡¦s not how Rockley presents content management. She begins with The basis of a unified content strategy and describes how content is created, who creates it, why authors work in isolation, and the consequences of isolation and centralizing content. The solution is to consolidate content in a definitive source, and a process that encourage authors to work collaboratively. The next step is to assess opportunities for content reuse. If you have never heard the term ¡¥reusing content,¡¦ you may know it as single sourcing. You probably already reuse content (i.e. copy and paste), which works well until the information, and everywhere that it appears, must be updated. Content reuse involves using existing content components (e.g. paragraphs, sections, and chapters) to develop new documents. Implementing a unified content strategy is a costly investment: tools, technologies, and training are not cheap. Investment costs are incurred in technology, training and consulting, and lost productivity.

Examples are given to calculate the cost of authoring tools, content management systems, training and consulting¡Xa content management system is not a plug and play, one size fits all solution. The return on investment is achieved by reduced time to market, reduced cost of product content development, improved accuracy and quality of content, and reduced manufacturing defects. The examples are especially helpful because you will need to create a proposal to convince budget holders and management on the return on investment of a content management solution.

Are you ready to buy a content management system? Not yet, read further. ¡§Performing a substantive audit: Determining business requirements¡¨ begins with an introduction on how to determine goals that you want a unified content strategy to solve, for example:
„h Reduce the time to plan, write, review, approve, and publish
„h Create flexible content that is easily reused to create information products for multiple products and multiple media
„h Reduce the cost of translation by reusing existing translations.
„h Make content more accessible; separating content from format makes it possible for content to be displayed automatically in a format appropriate to the disability.
Rockley describes how to identify opportunities where a unified approach of content management (i.e. planning, design, authoring and revision, version control, access control, publication and delivery to its audiences) is beneficial.

You are probably wondering how this all fits together, and Rockley explains how. ¡§Design¡¨ describes information modeling and metadata, how to personalize content, how to design a workflow, and how to implement your design.

An information model is critical for a unified content strategy because it provides a framework for documentation. It's the 80/20 rule: 80% of your effort is planning and analysis, and 20% of your effort is implementing the solution with whatever tools are selected to accomplish the goals the organization has set for itself. The level of detail of your information model depends on the level of reuse you want to achieve.

Many desktop publishing tools can dynamically publish personalized letters and forms by matching elements such as names and address¡Xa content management system can do the same. I was confused why design is given so much attention. Why not conduct the audit, buy the tools, and worry about design later? You can¡¦t. The design of information, reuse models/maps, meta data and workflow are all tool independent tasks. Regardless of the tools selected, you must first analyse and then design a content or information model so that it can be presented to IT staff and software vendors. Doing this in advance makes it possible for you to ask vendors to respond to a request for proposal and document how their tools can help you satisfy your specific challenges. Analysis provides an opportunity to collect metrics. From your information models, you can identify how much of your content could be reusable and where.

Educated on how content is used, where and how, you are better prepared to match the tools and technology to the origination¡¦s goals to deliver a unified content management solution. ¡§Tools and technologies¡¨ offers guidelines for evaluating tools. With so many tools and technologies to choose from, selecting the one that best satisfies your goals and budget is a challenge. Your best advantage is to be an educated consumer before you shop around. Rockley recommends that you identify your needs, and criteria for evaluating product options in terms of usability, training provided, supporting documentation provided, technical support, upgrades and enhancements, implementation time, cost, vendor viability, partnerships the vendor has to provide an expanded solution, and references. Where do you being looking?

Some good sources are conferences where vendors present authoring solutions such as the annual STC conference, electronic mailing lists, technology magazines, Web sites and online discussion boards and newsgroups. A supplement to ¡§Tools and technologies¡¨ is Appendix C, ¡§Vendors,¡¨ which is an overview of products, features and vendors. Appendix D, ¡§Tools Checklist,¡¨ which lists sample questions to ask a vendor. When you have narrowed your list of potential vendors, Rockley suggests that you either contact the vendors and request onsite demonstrations or send vendors an RFP (request for proposal).

¡§Tools and technologies¡¨ covers XML because it provides interoperability between applications. XML is not a set of tags that you apply to documents; it is a specification that sets rules for the creation of tag sets that you apply to documents. For instance, if you selected tools first and then designed your content, you might find that some of the content does not behave the way you expect it to. One solution would be to use XSLT to transform the content and move it around where you want it. While this may be an acceptable solution, it¡¦s not. The conversion costs time, money, and resources. There is no need to convert or transform content if it¡¦s modelled in XML from the start.

Rockley describes strategies for collaborative authoring, how to separate content from format, how to manage change and transition. An example is given to illustrate how the same product description is reused effectively to create a show catalog, brochure, press release and Web site. It¡¦s easy to understand that people find it hard to believe that content somebody else created could possibly meet their needs. After all, Rockley notes, it was written for a different purpose and media, and the author could not have known their customers/audience/requirements. However, if content is written for a different purpose, audience, or media without considering how the content can be reused, it¡¦ won¡¦t work.

Don¡¦t be optimistic that everybody will be willing to convert to a better way of authoring and managing content. Rockley presents issues to consider when planning your change management strategy such as overcoming resistance from opponents and descriptions of new and modified roles. She recommends creating a role for an enterprise project coordinator and information technologist; a change to existing roles business owners or analysts and information architects; and new skill sets (p. 413-415). Unintentionally overlooked are system administrators to maintain the content management system and to ensure that users adhere to standards.

Don¡¦t be overly optimistic that everybody will want morph into new roles and change their authoring habits. An XML system is best suited and ideal for a large documentation department for all content authoring or an organization where every author uses the XML authoring tool. A team of ten or fewer will be constrained to balance XML implementation and documentation project duties, and learn how to use the (new) content management system. Even if you assign the complex task of XML implementation and creation of information models, workflows and DTDs to a consultant, the consultant will require guidance from the team. These are only a few of the constraints to overcome to assure a successful unified content strategy that Rockley expertly describes how to overcome.

Managing Enterprise Content concludes with a checklist for implementing a unified content strategy, suggestions for writing for multiple media, sample questions to ask vendors, a checklist for the tools required to implement a unified content strategy, and the importance of content relationships in version control. Pay close attention to usability. The rollout of a content management system, authoring tools, and authoring standards affects every member of the organization. If it¡¦s not easy to learn, easy to use, easy to support, and easy to maintain, authors will revert to the traditional way of writing and managing content.

Read Managing Enterprise Content before you invest in a content management system and consulting fees. You will be an educated and informed customer and user when you begin shopping for a content management solution of your own.

This is a must read book if you are a developer, architect or in anyway related to technology.

As a newcomer to enterprise architecture this book educated me on possibilities for decisions to be made in designing an enterprise architect. It will also give you a language for describing existing characteristics of an existing enterprise application which may use some combination of the patterns describe in this book. The discussion of where to keep session state for a webapp was particularly helpful to me.

Even if you don't do "Enterprise Application" development, this book is a must have in your library. If you have been developing for more than a couple of years and you haven't seen 1/2 of the patterns in this book, then you are probably doing something wrong and this book could greatly help you.

Even if you do know 1/2 or more of the patterns in this book it is a great reference to the details of these patterns. Unless you are a Sophomore Software Engineering Student I'd recommend this book over the GoF book. Gof is a must have too, but if you can only have one. Get this one!

For me, this book is an invaluable reference for building business apps.

Want help choosing a framework? Want some guidance for solving common business problems? These patterns help solve these kinds of problems.

NOTE: I have tried to find other sources for these patterns, and I have only found Fowlers website, which is really only a summary and recommends purchasing the book.

This book has examples in both Java and C#. You can certainly use these patterns in .NET.

Under .NET you are not actually forced to use the Table Model. I think the purpose of this book is to help you realize this.

There are frameworks for .NET that use the Domain Model and Data Mapper patterns, but you would never know this unless you were familiar with the patterns in this book.

For me, reading this book didn't allow me to write new code, but it did allow me to understand my choice to use a particular framework/technique over another.

This book is a complete beginner's handbook for enterprise patterns.

1) The "Mapping to Relational Database Patterns" section discusses patterns that are completely intuitive. I recall logically coming to this conclusions when I started programming in Visual Basic in 99. Nothing new in this section.

2) The "Concurrency" section is criminal in nature and assumes that the application runs on high-cost server. Process-per-session? Thread-per-request? Come on!! Has the author missed out on the Reactor, Proactor and Active Object patterns (he does reference ACE but only as a reference). These patterns have been recognized as not scalable in the late 90s.

3)The distribution patterns are clearly incomplete and desire a lot of details.

If you're just starting out,as a System Architect :-), you'll find this useful. Otherwise, use MSDN or ACE for enterprise patterns.

This book is good for Call Mananger version 4.0+, but the latest IPT guide is probably Implementing Cisco Unified Communications Manager, Part 1 from May 2008. It covers Unified Call Manager version 6.0+, so be sure which version you need.

This is one of the best books, easy to read and understand. There are questions at the end of each chapter (which are short and to the point) that help you test yourself on what you learned.

As a technical instructor I have used this book for class lecture. This book has great organization, and coverage of the material. I reccomend this book to anyone looking for study material for CIPT.

This is the best Ciscopress book that I have read, and I have read a few. It explains everything very nicely from designing to implementing VOIP network, Cisco CallManager to handsets. I read this book and was then able to successfully implement VOIP/IPTEL network for the company I worked for. 100% worth the buy.

This book is first a general introduction to voice over internet protocol (VOIP) and to the specifics of the Cisco approach. The basic concept is simple, send your voice communications over the internet using packet switching is a lot cheaper than the traditional Bell system approach of circuit switching where your circuit is vastly underused.

Cisco has put their products together into a product line around their Cisco Unified CallManager product, a part of the Cisco direction called AVVID: Architecture for Voice, Video, and Integrated Data.

While this book has the obvious goal of getting you to pass the Cisco IP Telephony (CIPT - 642-444) exam, it goes beyond what most 'exam cram' books do and will make you much more knowledgable about actually working with the equipment and software. The book gives you a complete background rather than just a list of questions and canned answers.

This book is perfect for beginning photoshoppers etc. all the important adobe programs are included (7 programs in contrary to the 6 in 1 the that the picture claims). I had photoshop classes a few years ago so it was good to refresh my memory. I had never worked with indesign or the other adobe programs but luckely it is not hard to figure out. The book does include some good tips but sometimes help of others is needed. Thank god for google :)!
I do recommend this book if you are a beginner like I am. It points you in the right direction. But if you want to create print ready documents a higher level of knowledge is required. But with a lot of patience and energy you'll get a long way with help of this book.

Are you kidding me! I spend $400 for a Kindle then get a $3 discount off the paperback version? No way!

Good overall but too basic even for me who has virtually no experience with the Adobe suite. There are numerous editing mistakes as well. In one chapter the entire last half was missing the supporting screenshots.

I've finally plunked down a few bills and bought the suite. The CS3 is phenomenal, by the way. My only problem is, is that with the exception of some older versions of Photoshop and a couple of projects with Illustrator, this suite is essentially a whole new program.

After reading the reviews below, I decided to borrow this book from the library just to be sure it was worth the effort to buy. After a couple of weeks of going through various chapters, I bought the book from Amazon.

Just to be sure, this is a book for beginners and moderate users of the CS3. There are two other books that I bought "How to Cheat in Flash CS3" and "WOW, The Adobe Illustrator CS3 book" because both offer step by step illustrated examples and on CD-rom. But neither offers an expansive explanation of the use of the tools as The Dummies version. And, we talking close to 100 pages on this subject alone.

The Dummies is about 800 pages and is separated by each of the CS3 Design Suite programs. Also, authors Jennifer and Chris Smith, do a great job of interconnecting the different softwares.

If theres a downside to this, it's this: the book is printed on stock paper barely heavier than newsprint. The cover creases very easily, everything within the cover pages is in b/w. This point does prove a bit disconcerting as your eyes tends to skip over the printed tables. If you had the tables in color, it would reinforce the lesson the authors were attempting to get across. And, last but not least, the Dummies collection does not come with a cd-rom.

The Dummies for CS3 does what it sets out to do: provide reference material for those who have the CS3 Design suite. Period. And, it does it well. It is not flashy as the other books I just mentioned but to get started in learning about this terrific suite, this should be your first stop.

And, for what it offers, it is a heck of a lot cheaper than taking a class.

We agree with the previous reviewer that mentioned the "lack of detail" in this text. This book may be useful for absolute beginners; however, we would NOT recommend it to those of us whom want a good reference text on Adobe's most powerful programs.

The Creative Suite 3 MAMMOTH is virtually impossible to discuss within a limited number of pages; not to mention that this book attempts to reference SEVEN giant programs in one book. If studying for an exam, we would recommend Cliffnotes; however, this book affords great limits to the rest of us! Better texts or alternative resources and tutorials should be considered.

This book is great it has everithing you want to know about rfid thanks

The book was in excellent condition, and the service was prompt!

Are you a developer or systems architect or project manager? If you are, then this book is for you! Authors Bill Glover and Himanshu Bhatt, have done an outstanding job of writing a book that shows you how to get that first RFID prototype out the door.

Glover and Bhatt, begin by defining RFID and introduce some of the fundamental concepts. Then, the authors describe the parts of an RFID system, their relationships to each other, and some of the functional and service-level requirements specific to RFID.
Next, the authors describe the tags that attach an identity to an item and communicate that identity to readers. The authors then examine how tags talk to readers. They continue by describing the readers that communicate with tags and connect RFID-tagged items to the network. Then, the authors cover how readers talk to middleware and applications. They then describe the middleware that manages RFID information and edge devices. Next, they examine the storage and use of RFID information. Then, they discuss some of the specific concerns related to managing RFID devices on the edge of the network. Next, the authors discuss real concerns regarding the impact of RFID on security and privacy, as well as dispelling some of the myths. Finally, they continue by providing a look at where RFID may take you in the next few years.

This most excellent book allows you to understand the major elements in an RFID system. More importantly, it shows you how to divide work, set goals, and understand vendor proposals.

I found this book one of the top two books in the field of RFID; the othe rone being RFID+ by Dr. Paul Sanghera. This book offers a comprehensive coverage of the RFID topics. But if you are a beginner, you should read Dr. Sanghera's book befroe reading this one.
Excellent book; highly recommended.

I've read several RFID books and this one is excellent. Good overview, plenty of detail, well organized and well written (i.e. readable).

This book covers the new features included in version 3 of Nessus, including the file content and security check audits that are only available through a direct feed subscription. Other books make cover Nessus but do not cover these new features. I use Nessus with privacy and security audits. This book is a must if you are using Nessus in a professional capacity. I keep track of local security law changes for the United States, and other background regarding using Nessus as a consultant at computersecuritylaw.us. I also recommend this book to non-Nessus using computer security officers, with increased cyber-attacks one should really consider this or other similar product as part of your computer security program.

For those who are in the dark about Boolean operators, wildcards, and databases online this is the book for you. The book breaks down the search prcess and begins with the essentials for online searching then moves to database navigation then to types of databases and finally how to review and and teach others. Great illustrations and examples are found in the book as well as questions to answer at every chapter.

While the material is basic, it is the essentials that are needed for great online searches and helping other find the information they need. After reading and studing this book, I find that my search success has increased greatly and I will keep this book for future reference.

I was glad that I could find this book through Amazon, and it arrived in the condition as described. This item arrived within the 7 to 10 dayshipping period. I was happy that it did not take longer, as I had it in time for my class. :)