Share via

3.3.5.1.2.1.1 Construction of Cache Bitmap (Revision 1)

  • Article

The structure and fields of the Cache Bitmap (Revision 1) Secondary Drawing Order are specified in section 2.2.2.2.1.2.2. The order fields MUST be populated in accordance with this description.

The bitmaps that are cached by the Cache Bitmap (Revision 1) Secondary Drawing Order can be consumed by future MemBlt (see section 3.3.5.1.1.1.9) and Mem3Blt (see section 3.3.5.1.1.1.10) Primary Drawing Orders.

The bitmap data MUST NOT include a Compressed Data Header structure (see [MS-RDPBCGR] section 2.2.9.1.1.3.1.2.3) if the exclusion of this header was specified in the General Capability Set (see [MS-RDPBCGR] section 2.2.7.1.1).

The cache ID and cache index to use are selected by the server based on the management policies that are implemented (for example, an LRU policy might be in effect).

The Cache Bitmap (Revision 1) Order MUST NOT be sent to the client if support for bitmap caching was not specified using the Revision 1 Bitmap Cache Capability Set (see [MS-RDPBCGR] section 2.2.7.1.4.1). Furthermore, if client-side support for the MemBlt or Mem3Blt Primary Drawing Orders (specified using the Order Capability Set specified in [MS-RDPBCGR] section 2.2.7.1.3) does not exist, the Cache Bitmap (Revision 1) Order SHOULD NOT be sent to the client.