Protocol Details The methods comprising this interface MUST all return 0x00000000 on success, and a non-zero, implementation-specific error code on failure. Unless otherwise specified in the following sections, a server implementation of this protocol can choose any non-zero Win32 error value to signify an error condition, as discussed in section . The side of the Workstation Service Remote Protocol MUST NOT interpret returned error codes. The of the protocol MUST simply return error codes to the invoking application without taking any protocol action. Note that the client side and refer to the initiating and receiving ends of the protocol, respectively, rather than to client or versions of an operating system. These methods MUST all behave the same regardless of whether the server side of the protocol is running in a client or server version of an operating system. wkssvc Client Details Abstract Data Model No abstract data is required. Timers No protocol timers are required beyond used internally by the to implement resiliency to network outages, as specified in . Initialization The MUST create an connection to the remote computer, using the details specified in section . Message Processing Events and Sequencing Rules No sequence of method is imposed on this protocol. When a method completes, the values that the returns MUST be returned unmodified to the upper layer. The MUST ignore errors that the RPC returns and notify the application invoker of the received in the higher layer. Otherwise, no special message processing is required on the client beyond the processing required in the underlying RPC protocol. Timer Events There are no timer events. Other Local Events are no local events. wkssvc Server Details Abstract Data Model This section describes a conceptual model of possible data organization that an implementation maintains to participate in this protocol. The described organization is provided to facilitate the
Protocol Details The methods comprising this interface MUST all return 0x00000000 on success, and a non-zero, implementation-specific error code on failure. Unless otherwise specified in the following sections, a server implementation of this protocol can choose any non-zero Win32 error value to signify an error condition, as discussed in section . The side of the Workstation Service Remote Protocol MUST NOT interpret returned error codes. The of the protocol MUST simply return error codes to the invoking application without taking any protocol action. Note that the client side and refer to the initiating and receiving ends of the protocol, respectively, rather than to client or versions of an operating system. These methods MUST all behave the same regardless of whether the server side of the protocol is running in a client or server version of an operating system. wkssvc Client Details Abstract Data Model No abstract data is required. Timers No protocol timers are required beyond used internally by the to implement resiliency to network outages, as specified in . Initialization The MUST create an connection to the remote computer, using the details specified in section . Message Processing Events and Sequencing Rules No sequence of method is imposed on this protocol. When a method completes, the values that the returns MUST be returned unmodified to the upper layer. The MUST ignore errors that the RPC returns and notify the application invoker of the received in the higher layer. Otherwise, no special message processing is required on the client beyond the processing required in the underlying RPC protocol. Timer Events There are no timer events. Other Local Events are no local events. wkssvc Server Details Abstract Data Model This section describes a conceptual model of possible data organization that an implementation maintains to participate in this protocol. The described organization is provided to facilitate the
%5BMS-WKST%5D-171201.docx