Next in thread → Next in month →

[OASIS Issue Tracker] (ODATA-837) Example 28: replace $deltaToken with a valid custom query option

From
OASIS Issues Tracker <>
Date
2015-11-19T17:36:09+00:00
ID
Thread
[OASIS Issue Tracker] (ODATA-837) Example 28: replace $deltaToken with a valid custom query option
[ https://issues.oasis-open.org/browse/ODATA-837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Pizzo updated ODATA-837:
--------------------------------

    Proposal: Treat $deltatoken (all lower-case) as a reserved token that services can use in delta links, similar to how we have reserved $skiptoken.  (was: Use server-generated-secret instead of $deltaToken
Alternate Proposal: treat $deltaToken as a reserved token that services can use in delta links, similar to how we have reserved $skipToken.)

> Example 28: replace $deltaToken with a valid custom query option
> ----------------------------------------------------------------
>
>                 Key: ODATA-837
>                 URL: https://issues.oasis-open.org/browse/ODATA-837
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Protocol
>    Affects Versions: V4.0_ERRATA02
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>            Priority: Trivial
>             Fix For: V4.0_ERRATA03
>
>
> At least one reader of the spec mistook the example custom query option $deltaToken for part of the standard



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
Next in thread → Next in month →