From cae56586268197571b476b4fbd9dd1da031edfbd Mon Sep 17 00:00:00 2001 From: Z Date: Mon, 26 Jun 2017 08:59:58 +0200 Subject: [PATCH] Update asynchronous-tasks.md --- execution/asynchronous-tasks.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/execution/asynchronous-tasks.md b/execution/asynchronous-tasks.md index c97afc5..2c61486 100644 --- a/execution/asynchronous-tasks.md +++ b/execution/asynchronous-tasks.md @@ -1,5 +1,5 @@ # Asynchronous Tasks -If an API operation is asynchronous, but its progress could be tracked by a client, the response to such an asynchronous operation **MUST** return, in the case of success, the **202 Accepted** status code together with a `application/hal+json` representation of a new **task-tracking resource**. +If an API operation is asynchronous, but a client could track its progress, the response to such an asynchronous operation **MUST** return, in the case of success, the **202 Accepted** status code together with an `application/hal+json` representation of a new **task-tracking resource**. ## Task Tracking Resource The task-tracking resource **SHOULD** convey the information about the status of an asynchronous task. @@ -20,10 +20,7 @@ Retrieval of such a resource using the HTTP GET Request Method **SHOULD** be des ## Design Note - The asynchronous operation task-tracking resource can be either **polled** by client or the client might initially provide a **callback** to be executed when the operation finishes. In the case of callback, the API and its client MUST agree on what HTTP method and request format is used for the callback invitation. If built within adidas, the "client" API is also the subject of the adidas API guidelines. - -