Revision Summary Date Revision History Revision Comments 7/20/2007 0.1 Major MCPP Milestone 5 Initial Availability 9/28/2007 1.0 Major Updated and revised the technical content. 10/23/2007 1.0.1 Editorial Changed language and formatting in the technical content. 11/30/2007 2.0 Major Added and updated sections. 1/25/2008 2.0.1 Editorial Changed language and formatting in the technical content. 3/14/2008 2.0.2 Editorial Changed language and formatting in the technical content. 5/16/2008 2.0.3 Editorial Changed language and formatting in the technical content. 6/20/2008 3.0 Major Updated and revised the technical content. 7/25/2008 4.0 Major Updated and revised the technical content.
8/29/2008 4.1 Clarified the meaning of the technical content. 10/24/2008 5.0 Updated and revised the technical content. 12/5/2008 5.1 Clarified the meaning of the technical content. 1/16/2009 6.0 Major Updated and revised the technical content. 2/27/2009 6.1 Minor Clarified the meaning of the technical content. 4/10/2009 6.1.1 Editorial Changed language and formatting in the technical content. 5/22/2009 6.1.2 Editorial Changed language and formatting in the technical content. 7/2/2009 6.1.3 Editorial Changed language and formatting in the technical content. 8/14/2009 6.1.4 Editorial Changed language and formatting in the technical content.
9/25/2009 6.2 Clarified the meaning of the technical content. 11/6/2009 6.2.1 Editorial Changed language and formatting in the technical content. 12/18/2009 6.3 Minor Clarified the meaning of the technical content. 1/29/2010 6.4 Minor Clarified the meaning of the technical content. 3/12/2010 7.0 Major Updated and revised the technical content. 4/23/2010 8.0 Major Updated and revised the technical content. 6/4/2010 8.0.1 Editorial Changed language and formatting in the technical content. 7/16/2010 9.0 Major Updated and revised the technical content. 8/27/2010 9.0 None No changes to the meaning, language, or formatting of the technical content.
Validate and Dispatch call. the Reply message content. Send the Reply. Process the Message An implementation MUST determine the associated with the received message in an way. How the is processed depends on the transport information of the associated Channel, as specified in the following Transport Section specifying the process Server Object URI Format identifier TCP under The path subcomponent of the extracted from the of the The Content Type field of the TCP under The path subcomponent of the URI extracted from the RequestURIHeader of the message The Content Type field of the ContentTypeHeader HTTP under in the of the message Content-Type entity-header under Request URI in the Request-Line of the HTTP message Content-Type entity-header Binding to Server Object An implementation MUST look up the got from the message in the . If Server Object Table does not have the Server Object, then the Server Type Table MUST be looked up for the specified Server Object URI. If the Server Object URI is not found in both the tables, then a RemotingException MUST be constructed as specified in and the MUST be sent back to the client. If the Server Object URI is found in the Server Object Table, then the corresponding Server Object in the table MUST be used to dispatch the call. Otherwise, if the Server Object URI is found in the Server Type Table, then a new Server Object MUST be created. If the Boolean value for the Server Object URI in the Server Object Table indicated that the is a then the Server Object MUST be added to the Server Object Table. De-Serializing the Message Content An implementation MUST use the Content Type retrieved from the message to identify the of the as specified in the following table. Content Type Serialization format specification Mapping section SOAP-
. 46 A Abstract data client ( 49, 67) server ( 49, 62) 19 B 17 64 37 C 46 35 19 90 29 29 39 36 40 Client abstract data model ( 49, 67) triggered events ( 53, 68) initialization ( 53, 68) local events ( 61, 70) message processing ( 54, 70) 70 sequencing ( 54, 70) timer events ( 61, 70) timers ( 53, 67) 37 44 25 27 70 Constructing 67 66 37 44 37 38 68 37 42 D Data model - abstract client ( 49, 67) server ( 49, 62) 64 70 29 65 E 42 37 28 38 71 30 F 79 19 42 G 68 8 H Higher-layer triggered events client ( 53, 68) server ( 53, 63) 81 HTTP transport 22 22 22 23 23 I 26 83 83 14 Initialization client ( 53, 68) server ( 53, 62) 37 8 L 26 Local events client ( 61, 70) server ( 61, 67) M Mapping Array Instances ( 58, 60) Class Instances ( 57, 60) Enum Values ( 58, 60) 61 57