 Trade In this Item for up to £8.10
Get an extra £5 when you trade in books worth £10 or more until June 30, 2012. Trade in Pattern-oriented Software Architecture Vol 2: Patterns for Concurrent and Networked Objects for an Amazon.co.uk gift card of up to £8.10, which you can then spend on millions of items across the site. Trade-in values may vary (terms apply). Find more products eligible for trade-in.
|
Frequently Bought Together
Product details
|
More About the Author
Product Description
Review
–– Overload, September 2000
"Let me Start by saying that I highly recommend this book. If you are a reader of the expanding literature on pattern–oriented software design, rush out and buy this book! This book has the potential to be a seminal volume." ––Glenn E. Mitchell II, Ph.D.: Microsoft Office Pro; www.msofficepro.com; (5/30/01)
"...an excellent source of key architecture and design patterns...this is a key reference book for anyone serious about OO modeling."
––www.ambysoft.com
"Let me Start by saying that I highly recommend this book. If you are a reader of the expanding literature on pattern–oriented software design, rush out and buy this book! This book has the potential to be a seminal volume." ––Glenn E. Mitchell II, Ph.D.: Microsoft Office Pro; www.msofficepro.com; (5/30/01)
Review
This chapter introduces topics related to concurrent and networked objects. Read the first page
Concordance
Front Cover | Copyright | Table of Contents | Excerpt | Index | Back Cover
Suggested Tags from Similar Products(What's this?)Be the first one to add a relevant tag (keyword that's strongly related to this product)
|
Sell a Digital Version of This Book in the Kindle Store
What Other Items Do Customers Buy After Viewing This Item?
Customer Reviews
The book introduces patterns and pattern languages, presents a synopsis of the past, present, and future of patterns, and has an ample bibliography. However, the bulk of the text describes particular patterns in four groups.
1. Server access and configuration patterns are concerned with making services available to applications via OO interfaces as well as configuring applications dynamically.
2. Event handling patterns were, for me, the highlight of the book. These address alternative schemes for passing events to applications.
3. Synchronization patterns deal with ways of handling locking and will probably be fairly familiar to server developers.
4. Concurrency patterns describe ways of structuring a system into multiple threads in an OO style.
The concepts and abstractions presented are very helpful, but are also described in concrete terms. For example, the Reactor pattern talks about demultiplexing and dispatching service requests but the description goes right down to the level of a TCP/IP select operation. In short, the descriptions are useful for novice and expert alike as layers of detail are added to each pattern in a predictable order. This makes it easy to understand each pattern and skip the low-level implementation details on a first reading.
If you work on software servers, middleware, communications software, or distributed applications, I recommend that you read this book.
I found that one needs to _study_ the book and then rework the examples to fully appreciate the power of those patterns. To me, the Variations sections made lots of sense _after_ studying each pattern. I already feel empowered (to use a corporate term) with many new tricks and ideas that often seemed to be known only by very few.
However two things I think could be improved:
1) The patterns often tend to be wordy and repetitive (but one might argue that that serves to illustrate the point better.) 2) Example code for each pattern is distributed (hmm!) among many pages making it difficult to see how all parts fit together. I believe an extra section containing a fully worked example will enable people to immediately reuse those patterns.
Listmania!
Look for similar items by category
Look for similar items by subject
Feedback
- Would you like to update product info or give feedback on images?
- I am the Author, and I want to comment on my book.
- I am the Publisher, and I want to comment on this book.
|
