A
dynamic view allows a consumer application to specify a subset of data content in which it is interested. A providing application can choose to supply only this requested subset of content across all response messages. This filtering results in reduced data flow across the connection. View use can be leveraged across all non-administrative domain model types, where specific usage and support should be indicated in the model definition. The provider indicates its support for view requesting via the
SupportViewRequests Login attribute, as described in
Section 3.3.1. For more information on dynamic views, refer to the
Enterprise Message API C++ Edition Developers Guide.