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] Commented: (ODATA-298) Clarify Requesting Changes to entity sets that include Stream properties

    [ http://tools.oasis-open.org/issues/browse/ODATA-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33164#action_33164 ] 

Evan Ireland commented on ODATA-298:

We have seen quite a few offline scenarios in which clients need to be able to detect changed stream contents (so they can download and store only changed streams).

Are we looking to validate the use case with real-world examples (which I can provide if needed), or just wanting to defer this to post-V4 if not enough other folks think it is important?

> Clarify Requesting Changes to entity sets that include Stream properties
> ------------------------------------------------------------------------
>                 Key: ODATA-298
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-298
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Protocol 
>    Affects Versions: V4.0_WD01
>         Environment: [Applied]
>            Reporter: Evan Ireland
>            Assignee: Michael Pizzo
>             Fix For: V4.0_WD01
> This relates to the procotol spec (2013-03-12) section 10.3 Requesting Changes.
> If a client requests an entity set with change tracking enabled, then Stream contents will never be included inline (Streams have to be separately fetched).
> But it would be good to clarify that if the contents of some Stream properties have changed, then the client (via a delta link) asks for changes to an entity set, they will receive changed entities for any entities whose stream properties have had their content changed.

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]