OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Created: (ODATA-456) Don't require client to specify odata.trackchanges preference on each page


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

                 Key: ODATA-456
                 URL: http://tools.oasis-open.org/issues/browse/ODATA-456
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Bug
          Components: OData Protocol 
    Affects Versions: V4.0_CSD01
         Environment: [Proposed]
            Reporter: Michael Pizzo
             Fix For: V4.0_CSD02


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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]