DCS Dynamic Messaging Patterns
DCS Dynamic Messaging Patterns are core DCS components that let client applications communicate with services (both local and remote). They use WCF and WS standards to provide interoperability and extensibility.
DCS uses Dynamic Messaging Patterns to manage all interactions between the client and services, even if they are on the same computer. This allows developers to separate the client and service, which minimizes the impact on code if a service is moved to a separate or remote system. Dynamic Messaging Patterns, however, should not be used for communication between in-process components.
Dynamic Messaging Patterns allow information to be transported in a manner that is invisible to both clients and services, while communicating the context and providing access to the interfaces exposed by the services. In addition to simplifying the programming interface, this approach limits the parameters of service methods to specific business data for each service.
Typically, the context is a serializable class and is composed of two distinct sets of information:
Infrastructure context, which contains static information about the computer, is invisible to applications, and is managed by the Dynamic Messaging Patterns. Examples of information transported by the infrastructure context are:
-
- Name of the computer that makes the call
- Identification of the physical call
- Organizational information (for example, state name, city name, terminal name, and so on)
- Channel to which the computer belongs
Business context, which contains information about the execution environment of a specific call, regardless of the logic of each call. Examples of information transported by the business context are:
-
- User/work session that makes the call
- Organizational information (for example, state name, city name, terminal name, and so on)
- Operational environment (production, approval, and testing)
- Identity of the logical call