From a4c33efc15480c4ae01f29ef211b6b15f85ded6c Mon Sep 17 00:00:00 2001 From: ianschechtman Date: Mon, 13 May 2024 14:54:59 +0200 Subject: [PATCH] Update README.md --- rest-api-guidelines/execution/long-running-tasks/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rest-api-guidelines/execution/long-running-tasks/README.md b/rest-api-guidelines/execution/long-running-tasks/README.md index b94cee8..521ea7c 100644 --- a/rest-api-guidelines/execution/long-running-tasks/README.md +++ b/rest-api-guidelines/execution/long-running-tasks/README.md @@ -2,7 +2,7 @@ This section includes the recommended approaches to handling long running tasks (LRTs) in REST APIs. -You can identify a LRT quite easily. The main factor to consider are the metrics from latency of the endpoint. If it requiress tens of seconds even minutes we are facing a problem related to LRTs. +You can identify a LRT quite easily. The main factor to consider are the metrics from latency of the endpoint. If it requiress tens of seconds or even minutes we are facing a problem related to LRTs. LRTs cannot be handled in a regular straight synchronous call. The amount of commited recources at the network, client and server levels are huge when connections are blocked for several minutes.