3.16.1 Abstract Data Model

  • Article

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 explanation of how the protocol behaves. This document does not mandate that implementations adhere to this model as long as their external behavior is consistent with that described in this document.

The server maintains the following data elements:

  • ClientApplicationID: A string identifying the client application using the interface. This is mutable.

  • UserLocale: An LCID identifying the locale to use when generating localized results for operations performed by interfaces obtained by calling methods defined by this interface.  This is mutable.

  • HistoryList: A list of IUpdateHistoryEntry instances representing all history entries recorded by the update agent, sorted by date in descending order. Once initialized, this data element is never modified.