Uploaded image for project: 'OASIS Open Data Protocol (OData) TC'
  1. OASIS Open Data Protocol (OData) TC
  2. ODATA-456

Don't require client to specify odata.trackchanges preference on each page

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: V4.0_CSD01
    • Fix Version/s: V4.0_CSD02
    • Component/s: Protocol
    • Labels:
      None
    • Environment:

      [Applied]

      Description

      Today we require that, if a client wants change tracking on a paged result, they must specify odata.trackchanges preference on each page.

      It is much easier for the service to encode in the next link the fact that the client wants change tracking than to have the client have the logic to add this to each next page request (the service already has to hold on to the "low water mark" or other delta token from the initial request). The client can also specify the odata.changetracking preference on GET to delta link to signal they will want to continue tracking changes after apply the current set of changes.

        Attachments

          Activity

            People

            • Assignee:
              mikep Michael Pizzo
              Reporter:
              mikep Michael Pizzo
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: