3 Protocol Details

SharePoint

This protocol allows protocol servers to notify protocol clients of application-level faults using SOAP faults. Except where specified, these SOAP faults are not significant for interoperability, and protocol clients can interpret them in an implementation-specific manner.

This protocol allows protocol servers to perform implementation-specific authorization checks and notify protocol clients of authorization faults either using HTTP status codes or using SOAP faults as specified previously in this section.

Occasionally, instances occur where this web service’s WSDL specifies optionality (for example, minOccurs="0" and maxOccurs="1") that conflicts with the stated behavior in this document, or the document doesn’t contain the stated behavior. In such cases, where the document and the WSDL conflict, the document takes precedence.  In cases where the document doesn’t specify optionality, the argument has to be present, even if the WSDL specifies that the argument is optional (for example, minOccurs="0").

In cases where an argument is optional and the WSDL specifies both "minOccurs=0" and "Nillable=true", treat the argument as only "minOccurs=0".

The client side of this protocol is simply a pass-through. That is, no additional timers or other state is required on the client side of this protocol. Calls made by the higher-layer protocol or application are passed directly to the transport, and the results returned by the transport are passed directly back to the higher-layer protocol or application.

Except where specified, protocol clients SHOULD interpret HTTP status codes returned by the protocol server as specified in [RFC2616] (Section 10, Status Code Definitions).

Show: