[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (ODATA-306) Batch Request processing: Define server behavior, if one or more request(s) didn't succeed
[ http://tools.oasis-open.org/issues/browse/ODATA-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Pizzo updated ODATA-306:
--------------------------------
Proposal:
The server MUST process the N components of the Batch in the order received.
It continues processing until
the first request fails or the first change set fails.
If the processing is terminated after the component M (M<N) the response contains only the first M components; the N-M not processed components are not part of the response.
This is the standard processing behavior.
The client can request by a prefer header odata.continue-on-failure that the server should process all requests and change-sets not stopping if any failure occurs.
was:
The server MUST process the N components of the Batch in the order received.
It continues processing until
the first request fails or the first change set fails.
If the processing is terminated after the component M (M<N) the response contains only the first M components; the N-M not processed components are not part of the response.
This is the standard processing behavior.
The client can request by a prefer header odata.succeed-on-failure that the server should process all requests and change-sets not stopping if any failure occurs.
> Batch Request processing: Define server behavior, if one or more request(s) didn't succeed
> ------------------------------------------------------------------------------------------
>
> Key: ODATA-306
> URL: http://tools.oasis-open.org/issues/browse/ODATA-306
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: Bug
> Components: OData Protocol
> Affects Versions: V4.0_WD01
> Environment: [Proposed]
> Reporter: Martin Zurmuehl
> Fix For: V4.0_WD01
>
>
> The order of Change Sets and non-Change-Set operations in a Batch request is significant as a service MUST process the N components of the Batch in the order received.
> Currently only the behavior is described, if the last operation in sequence fails.
> How should the server react, if the first ChangeSet processing fails or if the first non-Change-Set operation fails? Should he terminated the processing or should he continue the processing? How is the Batch Respond Format defined, if the processing is terminated?
> The requests must be processed in sequence, so it would make sense to stop after the first failed request or change sets as a default behaviour.
--
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]