The Component’s Role in a Distributed System
In a distributed application, components contain classes that typically play one of two roles:
A provider of services
A container for information
Why the sharp distinction? In a distributed application, state is a critical issue (as discussed in Chapter 10). By using this distinction, you can separate classes that require state but don’t provide much functionality (the information packages) from classes that provide a collection of utility functions and are entirely stateless (the service providers).
Note
Programming veterans might notice that I’ve studiously avoided bringing business objects into this discussion. In Chapter 10, we’ll revisit the issue in more detail as we examine tiers and object modeling. ...
Get Microsoft® .NET Distributed Applications: Integrating XML Web Services and .NET Remoting now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
