-
Type: Improvement
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: V4.0_CS01
-
Fix Version/s: V4.0_CSD03
-
Component/s: ATOM Format, JSON Format, Protocol
-
Labels:None
-
Environment:
[Applied]
-
Proposal:
-
Resolution:
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.