[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=32877#action_32877 ]
Ralf Handl commented on ODATA-298:
----------------------------------
That can be difficult for the server, e.g. if the media streams are stored somewhere in the file system and the database backing the OData service only keeps track of the (local) file names.
I'd like to make implementing deltas as easy for servers as possible: having some delta information is valuable for the client. Better have some delta information for most of the services than perfect delta information for almost no service.
> 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: [Proposed]
> Reporter: Evan Ireland
> 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]