Share via

3.1.5.9 GetExtendedUpdateInfo

  • Article

Synopsis:

To optimize client/server communications, the SyncUpdates (section 3.1.5.7) method only downloads the "Core" metadata associated with an update revision. Additional metadata and the URLs of the revision content MUST be obtained by using this method.

Request Validation:

Parameter

Validation Conditions

Error Code

cookie

MUST be a valid cookie, issued by this server, that has not expired.

InvalidCookie, ServerChanged, or CookieExpired

revisionIDs

MUST be smaller than the maximum request value that the server specified in the return value of GetConfig().

InvalidParameter

infoTypes

MUST be present.

InvalidParameters

locales

MUST be present, if the infoTypes parameter contains either the Eula or the LocalizedProperties element.

InvalidParameters

Response:

Upon successful completion, the server MUST return a GetExtendedUpdateInfoResponse message to the client. The message MUST be composed as follows:

  • OutOfScopeRevisionIDs: The IDs of requested revisions that are not deployed to the client.

  • Updates: Metadata fragments associated with the requested revision that match one of the requested infoTypes.

  • FileLocations: For each requested revision that is deployed to the client, the URLs (in the update content directory) of the updates-associated content. The structure of the content directory is implementation-specific.<56>