3 Protocol Details
In the following sections, the schema definition might differ from the processing rules imposed by the protocol. The WSDL in this specification matches the WSDL that shipped with the product and provides a base description of the schema. The text that introduces the WSDL might specify differences that reflect actual Microsoft product behavior. For example, the schema definition might allow for an element to be empty, null, or not present but the behavior of the protocol as specified restricts the same elements to being non-empty, not null, and present.
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.
This protocol allows protocol servers to perform implementation-specific authorization checks and notify protocol clients of authorization faults as specified previously in this section.
This protocol allows protocol servers to perform implementation-specific localization of text in various messages. Except where specified, the localization of this text is an implementation-specific behavior of the protocol server and not significant for interoperability.
The following high-level sequence diagram illustrates the operation of the protocol.
A view session is created on a successful OpenWorkbook request, as specified in OpenWorkbook (section 184.108.40.206). A view session stops responding to operations after a successful call to the CloseWorkbook operation or after the view session has timed out.
A new workbook session is created on a successful OpenWorkbook request, as specified in OpenWorkbook. A new workbook session stops responding to operations after a successful call to the CloseWorkbook operation or after the new workbook session has timed out.
An edit session is created on a successful OpenWorkbook request, unless one already exists for the same workbook, as specified by the url element in OpenWorkbook. A new participant is added to the edit session on a successful OpenWorkbook request.
The current participant is removed from the edit session on a successful call to CloseWorkbook. An edit session stops responding to operations when all of its participants have been removed.
A request is created when a Web service operation starts running on the protocol server, and ends when the Web service operation finishes, when it is successfully cancelled by a CancelRequest call, or after the request has timed out.