[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-656) Requesting clarity on payload ordering constraints for clients
[ https://issues.oasis-open.org/browse/ODATA-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralf Handl updated ODATA-656: ----------------------------- Environment: Proposed Proposal: Explicitly state that clients need not support payload ordering constraints for request payload from client to server. was: Assuming it was never intended that clients need to support payload ordering constraints (for request payload from client to server), then state it explicitly. > Requesting clarity on payload ordering constraints for clients > -------------------------------------------------------------- > > Key: ODATA-656 > URL: https://issues.oasis-open.org/browse/ODATA-656 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Improvement > Components: OData JSON Format > Affects Versions: V4.0_OS > Environment: Proposed > Reporter: Evan Ireland > Priority: Minor > Labels: Clarification > Fix For: V4.01_WD01 > > > Section 4.4 Payload Ordering Constraints would appear to apply only to servers/services. > If there was any intent that it also (optionally) apply to request payload (from client to server), or even if not, we should be clear about this. -- 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]