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] (ODATA-950) Clarify what requests can be delta enabled


     [ https://issues.oasis-open.org/browse/ODATA-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Pizzo updated ODATA-950:
--------------------------------

    Proposal: 
Any GET request to retrieve one or more entities can be delta enabled by the service.

Reasoning:

- The entity set scenario is already well documented so nothing new there.

- The reason for the single entity case is mainly for singletons.  If a service has a singleton, a natural defining query would be for the singleton entity possibly with expands.  You could make the same argument for just single entities that are not singletons.  The main reason I see for allowing a single entity (singleton or otherwise) without any nested entities to be delta enabled is in the case where the entity is very large (i.e. lots of large properties).  In that case, the delta protocol could be used to return only the properties that have changed.

- A function can return a collection of entities so it should be able to return a delta link.

Add Singleton, NavigationProperty, and Function to AppliesTo of ChangeTracking term.

  was:
Any GET request to retrieve one or more entities can be delta enabled by the service.

Reasoning:

- The entity set scenario is already well documented so nothing new there.

- The reason for the single entity case is mainly for singletons.  If a service has a singleton, a natural defining query would be for the singleton entity possibly with expands.  You could make the same argument for just single entities that are not singletons.  The main reason I see for allowing a single entity (singleton or otherwise) without any nested entities to be delta enabled is in the case where the entity is very large (i.e. lots of large properties).  In that case, the delta protocol could be used to return only the properties that have changed.

- A function can return a collection of entities so it should be able to return a delta link.


> Clarify what requests can be delta enabled
> ------------------------------------------
>
>                 Key: ODATA-950
>                 URL: https://issues.oasis-open.org/browse/ODATA-950
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: Protocol
>         Environment: Proposed
>            Reporter: Matthew Borges
>            Assignee: Matthew Borges
>            Priority: Minor
>             Fix For: V4.01_CSD02
>
>
> The spec explicitly mentions returning delta links only in the context of retrieve entity set requests.  It doesn't explicitly state whether or not other types of requests can be delta enabled.  For example, can a function that returns a collection be delta enabled?  Can a request for a singleton with all related entities expanded be delta enabled (for this case it isn't clear the spec would actually allow a delta link to be returned)?
> We should clarify what requests can be delta enabled.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)


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