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 0.1.4 Editorial Changed language and formatting in the technical content. 7/2/2009 1.0 Major Updated and revised the technical content. 8/14/2009 1.1 Minor Clarified the meaning of the technical content. 9/25/2009 2.0 Updated and revised the technical content. 11/6/2009 2.1 Clarified the meaning of the technical content.
12/18/2009 2.2 Clarified the meaning of the technical content. 1/29/2010 2.3 Minor Clarified the meaning of the technical content. 3/12/2010 3.0 Updated and revised the technical content. 4/23/2010 3.0.1 Editorial Changed language and formatting in the technical content. 6/4/2010 3.0.2 Editorial Changed language and formatting in the technical content. 7/16/2010 3.0.2 None No changes to the meaning, language, or formatting of the technical content. 8/27/2010 4.0 Major Updated and revised the technical content. 10/8/2010 4.0 None No changes to the meaning, language, or formatting of the technical content. 11/19/2010 4.0 None No changes to the
However, WSPELD extensions only to the Pull WSDL operation among the five of them. Abstract Data Model See the abstract data model in the common processing section . Timers None. Initialization See the initialization in the common processing section . Message Processing Events and Sequencing Rules The Enumeration includes one operation to which WSPELD applies. Operation Description Pull Pulls the resultant in the context of a specific enumeration The request and response controls element specified in section could be a part of both Pull request and response messages, respectively. Pull This section specifies extensions to the Pull operation defined by WS-Enumeration . WS-Enumeration specifies that the Pull operation, which involves pulling fragments requested during Enumeration, is initiated by sending a Pull request message containing the Pull element inside a soapenv:Body element to the directory server. On successful processing of a Pull request message, the directory server is expected to return a Pull response message containing the resultant object fragments wrapped by a pullResponse element inside a soapenv:Body element. WSPELD specifies that the ad:controls element defined in section , if present, MUST be the child element of the Pull element in the request message and can be specified in any order in the presence of other child elements. However, for the response message, the protocol mandates that the ad:controls element, if present, MUST be the last child element of the PullResponse element. See the example in section for the WS-Enumeration [WSENUM] Pull request and response message with controls extension. Events None. Local Events None.
... ... ... ...--> <xsd:complexType name="AddResponseType" > <xsd:sequence> <xsd:element ref="wxf:ResourceCreated" /> <xsd:element ref="ad:controls" minOccurs="0" maxOccurs="1" /> </xsd:sequence> </xsd:complexType> <!--other elements defined by [MS-WSTIM] ... ... ... ... ... ...--> </xsd:schema>
Index A Abstract data model enumeration server ( 15, 19) resource server ( 15, 16) ResourceFactory server ( 15, 17) server ( 15, 16, 17, 19) ad:Controls 12 13 12 12 14 14 14 14 9 14 14 14 14 14 C 10 37 14 13 20 18 D Data - abstract enumeration server ( 15, 19) resource server ( 15, 16) ResourceFactory server ( 15, 17) server ( 15, 16, 17, 19) 14 22 17 14 E Elements 12 12 13 12 11 14 Enumeration server abstract data model ( 15, 19) initialization ( 15, 19) 19 message processing 19 19 overview ( 15, 18) sequencing rules 19 19 19 timers ( 15, 19) Events local - server ( 17, 18, 19) timer - server ( 17, 18, 19) Examples 20 22 23 24 20 F 10 G 23 16 6 14 I 27 27 8 Initialization enumeration server ( 15, 19) resource server ( 15, 16) ResourceFactory server ( 15, 18) server ( 15, 16, 18, 19) 6 L Local events 19 17 18 server ( 17, 18, 19) M Message processing enumeration server 19 19 resource server 17 16 16 17 ResourceFactory server 18 18 server ( 16, 18, 19)
Messages 12 14 14 14 14 14 13 14 11 11 14 11 14 11 14 14 13 14 11 11 14 11 11 14 11 N 11 7 O Operations 18 17 16 19 17 8 P 27 9 9 35 Protocol Details 15 24 19 17 R 7 8 7 9 Resource server abstract data model ( 15, 16) initialization ( 15, 16) 17 message processing 17 16 16 17 overview ( 15, 15) sequencing rules 17 16 16 17 17 timers ( 15, 16) ResourceFactory server abstract data model ( 15, 17) initialization ( 15, 18) 18 message processing 18 18 overview ( 15, 17) sequencing rules 18 18 18 timers ( 15, 18) S 14 Security 27 27 Sequencing rules enumeration server 19 19 resource server 17 16 16 17 ResourceFactory server 18 18 server ( 16, 18, 19) Server abstract data model ( 15, 16, 17, 19) 18 17 16 initialization ( 15, 16, 18, 19) events ( 17, 18, 19) message processing ( 16, 18, 19) 19 17 sequencing rules ( 16, 18, 19) timer events ( 17, 18, 19) timers ( 15, 16, 18, 19) Server - enumeration abstract data model ( 15, 19) initialization ( 15, 19) 19 message processing 19 19
overview ( 15, 18) sequencing 19 19 19 timers ( 15, 19) Server - resource abstract data model ( 15, 16) initialization ( 15, 16) 17 message processing 17 16 16 17 overview ( 15, 15) sequencing 17 16 16 17 17 timers ( 15, 16) Server - ResourceFactory abstract data model ( 15, 17) initialization ( 15, 18) 18 message processing 18 18 overview ( 15, 17) sequencing rules 18 18 18 timers ( 15, 18) 14 10 Syntax 14 attributes 14 14 14 13 14 elements 12 11 11 14 11 11 11 14 T Timer events 19 17 18 server ( 17, 18, 19) Timers enumeration server ( 15, 19) resource server ( 15, 16) ResourceFactory server ( 15, 18) server ( 15, 16, 18, 19) 37 11 Types 13 14 V 10 10 W 28