Read more
Languages like C#, VB .NET, and Delphi include built-in support for events, and these events become very powerful when they connect the objects and components of a system. Events make it possible for such parts to interact without any coupling. And the resulting parts can be developed and tested individuallywhich keeps the code clean and simple.
Component-based development (CBD) is an extension of object-oriented programming. CBD does away with the language and vendor-specific limitations of OOP, makes software reuse more practical and accelerates the development process. Event-based programming is the next logical step in CBD, and makes components more reusable due to their decoupled nature. But event-based systems are easier to develop, which means they're cheaper and more reliable than traditional OOP or CBD systems.
This book teaches you how to develop software based on parts that interact primarily through an event mechanism. You'll learn how to use events in many different situations, to solve recurring development problems without coupling. The book introduces Signal Wiring Diagram, a novel form of software diagram similar to the circuit diagrams used by hardware designers. The book concludes with a series of case studies, incorporating all featured concepts. In a nutshell, you'll want to pick up a copy of this book because it
- How to use an event-based paradigm to reduce or completely eliminate coupling between classes and components
- Describes components, including coordinators, workers, builders, binders, and routers
- Three complete case studies that model concepts being used to design small, medium, and large systems
List of contents
Coupling.- Events and Notifications.- Notification Delivery.- Notification Payloads.- A Survey of Commercial Systems.- Diagrams for Event-Based Systems.- Signal Wiring Diagrams.- The Mechanics of Event Firing.- Event-Based Interaction Patterns.- Functional Roles.- Case Study 1: A System Browser.- Case Study 2: A Pipelined HTTP Service.- Case Study 3: A Distributed Workflow System.
About the author
Ted Faison is an internationally recognized expert in object-oriented and component-based development. A twenty-year veteran of the computer industry, he is an active researcher, lecturer, and author; his firm has provided software consulting services and built systems of all sizes for corporate and governmental organizations since 1992. Ted lives in southern California with his wife and three children.
Summary
Languages like C#, VB .NET, and Delphi include built-in support for events, and these events become very powerful when they connect the objects and components of a system. Events make it possible for such parts to interact without any coupling. And the resulting parts can be developed and tested individuallywhich keeps the code clean and simple.
Component-based development (CBD) is an extension of object-oriented programming. CBD does away with the language and vendor-specific limitations of OOP, makes software reuse more practical and accelerates the development process. Event-based programming is the next logical step in CBD, and makes components more reusable due to their decoupled nature. But event-based systems are easier to develop, which means they're cheaper and more reliable than traditional OOP or CBD systems.
This book teaches you how to develop software based on parts that interact primarily through an event mechanism. You'll learn how to use events in many different situations, to solve recurring development problems without coupling. The book introduces Signal Wiring Diagram, a novel form of software diagram similar to the circuit diagrams used by hardware designers. The book concludes with a series of case studies, incorporating all featured concepts. In a nutshell, you'll want to pick up a copy of this book because it
- How to use an event-based paradigm to reduce or completely eliminate coupling between classes and components
- Describes components, including coordinators, workers, builders, binders, and routers
- Three complete case studies that model concepts being used to design small, medium, and large systems
