From c745f139135a67ae4c954145ca108df5d70521b7 Mon Sep 17 00:00:00 2001 From: Valerio Campanella Date: Fri, 14 Feb 2020 14:42:00 +0000 Subject: [PATCH] OS 4.4 release notes: fix incorrect info in flow api improvements section --- docs/source/release-notes.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/release-notes.rst b/docs/source/release-notes.rst index c13838693c..dbe5964db2 100644 --- a/docs/source/release-notes.rst +++ b/docs/source/release-notes.rst @@ -23,7 +23,7 @@ Flows API improvements Corda 4.4 introduces a new ``FlowLogic.await`` API that allows a CorDapp developers to suspend their flow when executing user-defined long-running operations (e.g. call-outs to external services, long-running DB operations). This prevents these long-running operations from blocking the flow thread, allowing other flows to progress in the interim. Previously, these operations had to be executed synchronously, blocking the flow thread. -The CorDapp developer can decide whether to run these asynchronous flow operations on a dedicated node pool, or to handle the threading themselves directly. +The CorDapp developer can decide whether to run these asynchronous flow operations in a dedicated thread pool, or to handle the threading themselves directly. Note that as before, the flow framework suspends automatically for certain operations (e.g. when waiting to receive a message from a counterparty). These suspensions do not have to be triggered explicitly.