Modeling of synchronization parameters implicitly generates data partition keys within the Unwired Server cache. Partition
keys define subsections of data within an MBO, enabling parallel data access to large MBO data sets.
For example,
you can refresh multiple partitions in parallel, or query one partition while another is being refreshed. In general,
partitions prevent serialized access to the cache.
Some best practices for defining partition keys include:
- Synchronization parameters should be defined
and mapped to all result-affecting load parameters. Failure to do so results in partitions being continuly
overwritten/deleted which leads to unexpected results in the mobile client.
- Result-affecting load parameters are those parameters of the EIS read operation that affect the
results of the operation. Some parameters may be information needed by the EIS but do not
actually affect the results of the read operation. For example; suppose an MBO is modeled using a Web Service
operation “getAllBooksByAuthor(AuthorName, userKey) where userKey is simply a mechanism to authenticate
a user and does not effect the results of the operation. For a given “AuthorName” the service will return the
same list of books regardless of the “userKey” value. In this case “userKey” is not a result-affecting parameter and
therefore should not be mapped to a synchronization key.