[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (ODATA-307) Return odata.etag in collections also for odata=minimalmetadata
[ http://tools.oasis-open.org/issues/browse/ODATA-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Drees updated ODATA-307: ------------------------------- Resolution: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/48904/odata-json-format-v4.0-wd01-2013-4-23.docx Accepted: https://www.oasis-open.org/committees/download.php/49026/odata-meeting-34_on-20130425_26-F2F-minutes.html#odata-307 was:https://www.oasis-open.org/apps/org/workgroup/odata/download.php/48904/odata-json-format-v4.0-wd01-2013-4-23.docx > Return odata.etag in collections also for odata=minimalmetadata > --------------------------------------------------------------- > > Key: ODATA-307 > URL: http://tools.oasis-open.org/issues/browse/ODATA-307 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Bug > Components: OData JSON Format > Affects Versions: V4.0_WD01 > Environment: [Applied] > Reporter: Ralf Handl > Assignee: Michael Pizzo > Fix For: V4.0_WD01 > > > For single entity responses the ETag is contained in the ETag response header. > For multi-entity responses the header is not sufficient, instead clients need to receive the ETag in the entity metadata, i.e. the odata.etag annotation. > We do have a Core annotation that tells clients which entity properties influence the ETag, but we currently have no way of telling the client which algorithm the server uses to calculate the ETag. -- 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]