Content Synchronization: The client can request update content comprised of any associated with the updates required by the client. Reporting: The client reports events to the server that provide information on its update-related activities (for example, content download succeeded or failed; content install succeeded or failed). Reports are generated asynchronously from the rest of the protocol. A UML sequence diagram can be found in section 3.1.5. This specification details the protocol mechanisms that enable clients to download binaries, synchronize update metadata , and download update content. It also details the protocol mechanisms for enabling clients to report events to servers. Relationship to Other Protocols The reporting and synchronization protocols include that use (as specified in ) over HTTP or HTTPS (as specified in ) for communication. The and content synchronization protocols use HTTP 1.1 ([RFC2616]). Figure 1: Relationship between protocols related to this protocol Content download (both update content and ) uses HTTP 1.1 HEAD and GET (Range) requests (as specified in [RFC2616] sections 9.3 and 9.4). This specification is closely related to the Windows Server Update Services: Server-Server Protocol, as specified in , which defines mechanisms for synchronizing updates within a hierarchical configuration of . Prerequisites/Preconditions This protocol imposes the following requirement on server implementations. This document specifies how the binaries and are distributed the Client-Server Communications Protocol. It does not specify the format of the binaries or metadata themselves, but it assumes that the metadata is well-formed XML and is compatible with the XPATH queries specified in section for populating the server data model. In all other respects, the binaries and metadata are treated as opaque by the server. This protocol imposes the following requirement on client implementations. Clients are required to be configured to obtain updates from the server. This configuration can be performed manually or, in managed environments, by an appropriate form of centralized machine configuration. Applicability Statement This protocol is applicable in environments where there is a need for centralized, systematic distribution of software updates to managed . Versioning and Capability Negotiation This specification covers versioning issues in the following areas. Client protocol versions: are different versions of the client side of the protocol. The latest client protocol version is specified in section . Differences in behavior due to client protocol versions are specified in several sections:
Content Synchronization: The client can request update content comprised of any associated with the updates required by the client. Reporting: The client reports events to the server that provide information on its update-related activities (for example, content download succeeded or failed; content install succeeded or failed). Reports are generated asynchronously from the rest of the protocol. A UML sequence diagram can be found in section 3.1.5. This specification details the protocol mechanisms that enable clients to download binaries, synchronize update metadata , and download update content. It also details the protocol mechanisms for enabling clients to report events to servers. Relationship to Other Protocols The reporting and synchronization protocols include that use (as specified in ) over HTTP or HTTPS (as specified in ) for communication. The and content synchronization protocols use HTTP 1.1 ([RFC2616]). Figure 1: Relationship between protocols related to this protocol Content download (both update content and ) uses HTTP 1.1 HEAD and GET (Range) requests (as specified in [RFC2616] sections 9.3 and 9.4). This specification is closely related to the Windows Server Update Services: Server-Server Protocol, as specified in , which defines mechanisms for synchronizing updates within a hierarchical configuration of . Prerequisites/Preconditions This protocol imposes the following requirement on server implementations. This document specifies how the binaries and are distributed the Client-Server Communications Protocol. It does not specify the format of the binaries or metadata themselves, but it assumes that the metadata is well-formed XML and is compatible with the XPATH queries specified in section for populating the server data model. In all other respects, the binaries and metadata are treated as opaque by the server. This protocol imposes the following requirement on client implementations. Clients are required to be configured to obtain updates from the server. This configuration can be performed manually or, in managed environments, by an appropriate form of centralized machine configuration. Applicability Statement This protocol is applicable in environments where there is a need for centralized, systematic distribution of software updates to managed . Versioning and Capability Negotiation This specification covers versioning issues in the following areas. Client protocol versions: are different versions of the client side of the protocol. The latest client protocol version is specified in section . Differences in behavior due to client protocol versions are specified in several sections: