Revision Summary Date Revision History Revision Class Comments 2/22/2007 0.01 New Version 0.01 release 6/1/2007 1.0 Major Updated and revised the technical content. 7/3/2007 1.0.1 Editorial Changed language and formatting in the technical content. 7/20/2007 1.0.2 Editorial Changed language and formatting in the technical content. 8/10/2007 1.0.3 Editorial Changed language and formatting in the technical content. 9/28/2007 1.0.4 Editorial Changed language and formatting in the technical content. 10/23/2007 1.0.5 Editorial Changed language and formatting in the technical content. 11/30/2007 1.0.6 Editorial Changed language and formatting in the technical content.
1/25/2008 1.0.7 Editorial Changed language and formatting in the technical content. 3/14/2008 1.0.8 Editorial Changed language and formatting in the technical content. 5/16/2008 1.0.9 Editorial Changed language and formatting in the technical content. 6/20/2008 1.1 Minor Clarified the meaning of the technical content. 7/25/2008 1.1.1 Editorial Changed language and formatting in the technical content. 8/29/2008 1.1.2 Editorial Changed language and formatting in the technical content. 10/24/2008 1.2 Clarified the meaning of the technical content. 12/5/2008 2.0 Major Updated and revised the technical content. 1/16/2009 2.0.1 Editorial Changed language and formatting
in the technical content. 2/27/2009 2.0.2 Editorial Changed language and formatting in the technical content. 4/10/2009 2.0.3 Editorial Changed language and formatting in the technical content. 5/22/2009 3.0 Major Updated and revised the technical content. 7/2/2009 3.1 Minor Clarified the meaning of the technical content. 8/14/2009 3.2 Minor Clarified the meaning of the technical content. 9/25/2009 3.3 Minor Clarified the meaning of the technical content. 11/6/2009 4.0 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.
meaning, language, or formatting of the technical content. 2/11/2011 7.1 Minor Clarified the meaning of the technical content. 3/25/2011 8.0 Major Updated and revised the technical content. 5/6/2011 8.0 None No changes to the meaning, language, or formatting of the technical content. 6/17/2011 8.1 Minor Clarified the meaning of the technical content. 9/23/2011 8.1 None No changes to the meaning, language, or formatting of the technical content. 12/16/2011 9.0 Updated and revised the technical content. 3/30/2012 9.0 None No changes to the meaning, language, or formatting of the technical content.
meaning, language, or formatting of the technical content. 6/30/2015 10.0 Major Significantly changed the technical content. 10/16/2015 10.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 11.0 Significantly changed the technical content. 6/1/2017 11.0 None No changes to the meaning, language, or formatting of the technical content. 9/15/2017 12.0 Major Significantly changed the technical content. 12/1/2017 12.0 None No changes to the meaning, language, or formatting of the technical content.
The receiver of the MUST first validate the common header for consistency (section ). If the size is not long enough to contain all the fields in the message, the connection SHOULD be terminated.<24> Receipt of this PDU indicates that the graphic stream is no longer paused (section ). The PDU is stateless and has no sequencing rules. Timer Events None. Other Local Events None. Sharing Manager Details Abstract Data Model Refer to the common details abstract data model in section . Timers None. Initialization Before messages can be sent, the static virtual channel MUST be established by using the parameters specified in section . Higher-Layer Triggered Events None. Message Processing Events and Sequencing Rules Application and Window Filtering Processing the Show Window PDU The receiver of the MUST verify the common header for consistency (section ). If the size is not long enough to contain all the fields in the message, the connection SHOULD be terminated.<25> The WndId field in the PDU MUST specify the window that the wants to view. The SHOULD <26> validate the WndId field against the existing windows and SHOULD <27> verify that the participant is entitled to make that request before granting it. Participant Management Processing a Participant-Created PDU See section .<28> Processing a Participant-Removed PDU