mirror of
https://github.com/hyperledger/fabric-samples.git
synced 2026-06-17 15:35:09 +00:00
Correcting line in Fabric Gateway client to be like in Legacy
Signed-off-by: munapower <mmunaro@hotmail.com>
This commit is contained in:
parent
8146364af4
commit
644d359d63
1 changed files with 1 additions and 1 deletions
|
|
@ -48,7 +48,7 @@ In order for the client application to operate effectively, it must make use of
|
|||
|
||||
## Fabric Gateway client API
|
||||
|
||||
The following diagram demonstrates for the transaction submit flow how it is executed for a client using the Fabric Gateway client API. Solid orange lines represent interactions between the client and a Gateway peer, which must cross the firewall at the boundary of the network deployment. Dashed green lines represent interactions between network nodes.
|
||||
The following diagram demonstrates how the transaction submit flow is executed for a client using the Fabric Gateway client API. Solid orange lines represent interactions between the client and a Gateway peer, which must cross the firewall at the boundary of the network deployment. Dashed green lines represent interactions between network nodes.
|
||||
|
||||
Notice that the client only needs to interact directly with the Gateway peer. The Gateway peer operates as a client driving the transaction submit flow from within the network deployment on behalf of the client application.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue