Invoke方法的调用是异步的吗？
Is the call of Invoke method asynchronous?
不知道Invoke方法的调用是不是异步的？希望有人能解释一下。如果你能提供一些描述它的文件，那就太好了。
是的。根据 Hyperledger Fabric 文档，Invoke 事务的事务执行是异步的。
The response to a chaincode invocation request will contain a status
element confirming successful completion of the request. The response
will likewise contain the transaction id number for that specific
transaction. The client may use the returned transaction id number to
check on the status of the transaction after it has been submitted to
the system, as the transaction execution is asynchronous
只是为了更清楚地引用 cjcroix 的回答，Fabric 文档在 fabric 文档中指定了与 REST API 相关的以下语句
[Fabric Documentation : CORE API]
"The response to a chaincode invocation request will contain a status element confirming successful completion of the request. "
但是status这里只是提交过程的状态。调用的实际状态如下一行所述，具体取决于您尝试调用的代码的逻辑
The client may use the returned transaction id number to check on the status of the transaction after it has been submitted to the system, as the transaction execution is asynchronous.
不知道Invoke方法的调用是不是异步的？希望有人能解释一下。如果你能提供一些描述它的文件，那就太好了。
是的。根据 Hyperledger Fabric 文档，Invoke 事务的事务执行是异步的。
The response to a chaincode invocation request will contain a
statuselement confirming successful completion of the request. The response will likewise contain the transaction id number for that specific transaction. The client may use the returned transaction id number to check on the status of the transaction after it has been submitted to the system, as the transaction execution is asynchronous
只是为了更清楚地引用 cjcroix 的回答，Fabric 文档在 fabric 文档中指定了与 REST API 相关的以下语句 [Fabric Documentation : CORE API]
"The response to a chaincode invocation request will contain a status element confirming successful completion of the request. "
但是status这里只是提交过程的状态。调用的实际状态如下一行所述，具体取决于您尝试调用的代码的逻辑
The client may use the returned transaction id number to check on the status of the transaction after it has been submitted to the system, as the transaction execution is asynchronous.