Interface DsRequestEquivalence

public interface DsRequestEquivalence

Various subsystems have a need to compare DataSource requests and understand if they are equivalent or affect the same data (examples include automatic cache synchronization and offline caching and synchronization).

Aside from basic properties that would clearly make two DSRequests non-equivalent (dataSource, operationType and data, as well as sortBy, startRow, endRow and textMatchStyle for a "fetch"), operationId is the only property that will cause two DSRequests to be considered distinct (non-equivalent) requests.

Bearing this in mind, the best practice is: