Revision Summary Date Revision History Revision Class Comments 12/5/2008 0.1 Major Initial Availability. 1/16/2009 0.1.1 Editorial Changed language and formatting in the technical content. 2/27/2009 0.1.2 Editorial Changed language and formatting in the technical content. 4/10/2009 0.1.3 Editorial Changed language and formatting in the technical content. 5/22/2009 1.0 Major Updated and revised the technical content. 7/2/2009 2.0 Major Updated and revised the technical content. 8/14/2009 3.0 Major Updated and revised the technical content. 9/25/2009 3.1 Minor Clarified the meaning of the technical content. 11/6/2009 4.0 Major Updated and revised the technical content.
12/18/2009 5.0 Major Updated and revised the technical content. 1/29/2010 6.0 Updated and revised the technical content. 3/12/2010 6.0.1 Editorial Changed language and formatting in the technical content. 4/23/2010 6.0.2 Editorial Changed language and formatting in the technical content. 6/4/2010 6.0.3 Editorial Changed language and formatting in the technical content. 7/16/2010 6.0.3 None No changes to the meaning, language, or formatting of the technical content. 8/27/2010 6.0.3 None No changes to the meaning, language, or formatting of the technical content. 10/8/2010 6.0.3 None No changes to the meaning, language, or formatting
of the technical content. 11/19/2010 6.0.3 None No changes to the meaning, language, or formatting of the technical content. 1/7/2011 6.0.3 None No changes to the meaning, language, or formatting of the technical content. 2/11/2011 6.0.3 None No changes to the meaning, language, or formatting of the technical content. 3/25/2011 6.0.3 None No changes to the meaning, language, or formatting of the technical content. 5/6/2011 6.0.3 None No changes to the meaning, language, or formatting of the technical content. 6/17/2011 6.1 Minor Clarified the meaning of the technical content.
9/23/2011 6.1 None No changes to the meaning, language, or formatting of the technical content. 12/16/2011 7.0 Major Updated and revised the technical content. 3/30/2012 7.0 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 7.0 None No changes to the meaning, language, or formatting of the technical content. 10/25/2012 7.0 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 7.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 8.0 Major Updated and revised the technical content.
terminated, no other communication over the Remote Desktop Protocol: Desktop Composition Virtual Channel Extension occurs. Applicability Statement The Remote Desktop Protocol: Desktop Composition Virtual Channel Extension is designed to be run within the context of a Remote Desktop Protocol Virtual Channel established between a client and a server. This protocol applies to driving a used in conjunction with a compositor. Versioning and Capability Negotiation The Remote Desktop Protocol: Desktop Composition Virtual Channel Extension does not implement any version negotiation. All capability negotiation is specified in section 1.7. Vendor-Extensible Fields The Remote Desktop Protocol: Desktop Composition Virtual Channel Extension contains no fields. Standards Assignments The Remote Desktop Protocol: Desktop Composition Virtual Channel Extension does not use any assigned standard.
Messages Transport The Remote Desktop Protocol: Desktop Composition Virtual Channel Extension messages are passed between the and the embedded within a Remote Desktop Protocol connection, as specified in section 2.1. The Remote Desktop Protocol: Desktop Composition Virtual Channel Extension itself does not establish any transport connections. Message Syntax Desktop Composition Mode Management Drawing and Desktop Mode Changes Order (TS_COMPDESK_TOGGLE) The server the TS_COMPDESK_TOGGLE packet to the client to communicate changes in the drawing mode and in the desktop mode. The drawing mode indicates whether the is turned on. The drawing mode changes as a result of enabling and disabling desktop composition. The desktop mode indicates whether the current desktop is the one that is being composed if is turned on. The desktop mode changes as a result of . 0 1 2 3 4 5 6 7 8 9 1 0 1 2 3 4 5 6 7 8 9 2 0 1 2 3 4 5 6 7 8 9 3 0 1 header operation size eventType header (1 byte): An 8-bit unsigned integer. An alternate secondary order header, as specified in section 2.2.2.2.1.3.1.1. The embedded order type field MUST be set to TS_ALTSEC_COMPDESK_FIRST (0x0c). operation (1 byte): An 8-bit unsigned integer. The operation code. This field MUST be set to COMPDESKTOGGLE (0x01). size (2 bytes): A 16-bit unsigned integer. The size of the order data that follows the size field. This field MUST be set to 0x0001. eventType (1 byte): An 8-bit unsigned integer. The specific event that is being signaled to the client to change its drawing and desktop mode. It MUST have one of the following values: Meaning REDIRMODE_COMPOSITION_OFF 0x00 The server is leaving desktop composition mode. REDIRMODE_RESERVED_00 0x01 This value is reserved and not used. It SHOULD be ignored if received. REDIRMODE_RESERVED_01 This value is reserved and not used. It SHOULD be ignored if received.
Index A Abstract data model client ( 20, 21) server ( 20, 23) 11 C 12 33 Client abstract data model ( 20, 21) higher-layer triggered events ( 20, 21) 21 local events ( 21, 23) message processing ( 20, 21) 23 sequencing rules ( 20, 21) timer events ( 20, 23) timers ( 20, 21) Closing drawing order ( 23, 26, 28) D Data model - abstract client ( 20, 21) server ( 20, 23) 8 21 28 9 13 24 Desktop state changes order ( 21, 25, 28) Drawing operations ( 10, 18, 23, 26, 28) Drawing order closing ( 23, 26, 28) retargeting ( 23, 26, 28) Drawing state changes order ( 21, 25, 28) E 28 F 12 G 6 H Higher-layer triggered events client ( 20, 21) server ( 20, 24) I 31 31 7 Initialization 21 24 6 L Local events client ( 21, 23) server ( 21, 27) 10 M Message processing client ( 20, 21) server ( 20, 24) Messages 9 14 13 13 N 7 O Other local events 23 27 8 8 P 11 11 32 R 14 Redirection surface management ( 10, 14, 22, 22, 25, 25, 29, 29) 7 7 7 11 8 Retargeting drawing order ( 23, 26, 28) S 31 31 Sequencing rules client ( 20, 21) server ( 20, 24)