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] Updated: (ODATA-110) Track Prefer Header in Http


     [ http://tools.oasis-open.org/issues/browse/ODATA-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Pizzo updated ODATA-110:
--------------------------------

       Proposal: 
Rename "return-content" to "return=representation" and "return-no-content" to "return=minimal" in both Prefer and Preference-Applied headers. Use OData-31 to track use of the "respond-async" preference.

Existing implementations are free to continue to use "return-content" and "return-no-content' as synonyms, but this does not need to be spelled out in the OASIS specification.

Note that Preference-Applied has been resurrected, and is defined to be the same preference tokens as defined for the Prefer (but without parameters).
    Environment: [Proposed]

Prefer is now approved (see http://datatracker.ietf.org/doc/draft-snell-http-prefer/?include_text=1). We should snap to the approved definition as proposed.

> Track Prefer Header in Http
> ---------------------------
>
>                 Key: ODATA-110
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-110
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData Protocol v1.0
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>
> OData uses the Prefer and PreferenceApplied headers defined in http://tools.ietf.org/html/draft-snell-http-prefer-01. Since introducing the Prefer header to OData, the values for "return-content" and "return-no-content" have changed (draft 12 uses "return-minimal" and "return-representation") and the PreferenceApplied header has been removed.
> The Prefer header is still in draft and may change, revert back to previous values, or expire.
> We should track such changes to Prefer, either by updating the OData specification, or by keeping the OData specification current and, if/when Prefer is final, defining the final values as synonyms.

-- 
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]