[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (ODATA-199) $expand should be allowed to return only ids for already seen objects
[ http://tools.oasis-open.org/issues/browse/ODATA-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralf Handl updated ODATA-199:
-----------------------------
Proposal:
Propose we support Entity References as described in https://www.oasis-open.org/apps/org/workgroup/odata/download.php/48082/latest with a preference of odata.allow-references
Accepted: https://www.oasis-open.org/committees/download.php/48097/odata-meeting-23_on-20130130_31-F2F-minutes.html#odata-199
was: Propose we support Entity References as described in: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/48082/latest
> $expand should be allowed to return only ids for already seen objects
> ---------------------------------------------------------------------
>
> Key: ODATA-199
> URL: http://tools.oasis-open.org/issues/browse/ODATA-199
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: Improvement
> Components: OData ATOM Format v1.0, OData JSON Format v1.0
> Environment: [Proposed]
> Reporter: Michael Pizzo
> Priority: Minor
>
> Today, specifying $expand may return the same item multiple times. For example, if the someone is really popular, selecting ~people/$expand=friends may return the same friend for multiple people. This can lead to payload bloat when attempting to select a graph of related entities.
> A simple means of compression would be to allow the service to return only the id of related entities that have already been returned within a feed. This would work nicely for existing clients that track incoming entities as they generally already have logic to merge with or simply return previously retrieved objects.
> We might consider a preference to allow the client to request whether or not duplicate ids are returned in full, and pick a default behavior for the service if the client doesn't specify a preference. We could use the defined return=minimal for this; currently this is used in PUT/POST to say don't return results if they haven't changed, but are undefined for a GET operation in OData.
--
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]