From 067b627416d3eb5cebaf39897b683847fc4b1ca9 Mon Sep 17 00:00:00 2001 From: lesleyannj Date: Thu, 3 Oct 2019 09:31:59 +0100 Subject: [PATCH] [FABN-1335]-Reference event handling Signed-off-by: lesleyannj Change-Id: I843be29b366c10e9943be310b53f83fa54481331 --- docs/tutorials/transaction-commit-events.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/tutorials/transaction-commit-events.md b/docs/tutorials/transaction-commit-events.md index cb5cbb58ba..a1d43e4e84 100644 --- a/docs/tutorials/transaction-commit-events.md +++ b/docs/tutorials/transaction-commit-events.md @@ -52,7 +52,7 @@ await gateway.connect(connectionProfile, connectOptions); Specifying `null` as the event handling strategy will cause transaction invocations to return immediately after successfully sending the endorsed transaction to the orderer. It will not wait for any commit events to be -received from peers. +received from peers. For more details on *Event Handling Options*, see [DefaultEventHandlerOptions](module-fabric-network.Gateway.html#~DefaultEventHandlerOptions__anchor). ### Plug-in event handlers @@ -83,6 +83,8 @@ const gateway = new Gateway(); await gateway.connect(connectionProfile, connectOptions); ``` +For more details on *Event Handling Options*, see [DefaultEventHandlerOptions](module-fabric-network.Gateway.html#~DefaultEventHandlerOptions__anchor). + The *transaction event handler* object returned must implement the following lifecycle functions.