[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-585) Status response message as carrier for annotations as alternative to 204 No Content
[ https://tools.oasis-open.org/issues/browse/ODATA-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37597#comment-37597 ] Michael Pizzo commented on ODATA-585: ------------------------------------- I would think this would be really confusing to the client to get back a different resource than the one requested. Why wouldn't we instead define a header (or headers) to convey this information, rather than defining new semantics for http status codes? > Status response message as carrier for annotations as alternative to 204 No Content > ----------------------------------------------------------------------------------- > > Key: ODATA-585 > URL: https://tools.oasis-open.org/issues/browse/ODATA-585 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Improvement > Components: OData Protocol > Affects Versions: V4.0_COS > Environment: [Proposed] > Reporter: Ralf Handl > Fix For: V4.1_WD01 > > > There are some situations where OData 4.0 requires a response with 204 No Content: > 1. GET a raw primitive value using the /$value path suffix and the value is null > 2. GET a nullable property or navigation property and the value is null > 3. DELETE a nullable property or relationship to set it to null > 4. GET a function result that is primitive or structured and is null > 5. POST an action call and the primitive or structured result is null, or the action has no result > This does not allow to add explanatory annotations to the logically empty result. -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]