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-539) Delta response encoding is unnecessarily verbose and change type is missing when odata.metadata=none

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

Ralf Handl commented on ODATA-539:

Even for odata.metadata=none deleted entities, added links, and deleted links MUST contain the odata.context, so there's no need for an additional annotation.

All URLs can be relative, and it is in the interest of servers to produce relative URLs so they can be placed behind a proxy and used in enterprise scenarios, see ODATA-527. We don't need to require that.

> Delta response encoding is unnecessarily verbose and change type is missing when odata.metadata=none
> ----------------------------------------------------------------------------------------------------
>                 Key: ODATA-539
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-539
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData ATOM Format , OData JSON Format, OData Protocol 
>    Affects Versions: V4.0_WD01
>            Reporter: Evan Ireland
>             Fix For: V4.0_WD01
> For a number of reasons, the encoding of delta responses is unnecessarily verbose, which will result in excessive network and CPU utilization, particularly for offline-enabled mobile devices.
> (1) To distinguish between changed entity, deleted entity, changed link, or deleted link requires use of the Context URL which, as described in ODATA-538, can be unnecessarily verbose.
> (2) The "id" in deleted entities and the "source"/"target" in added/deleted links is not required to use a relative URL, and clients cannot control whether the server will or will not use relative URLs.
> Additionally, if odata.metadata=none, clients may be unable to decode delta responses, since odata.context may be omitted in that case. Interestingly, odata.deltaLink cannot be omitted from the response, although a delta response without change type for each of the included changes would be useless to a client.

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]