使用Fabric CLI执行peer命令时，谁负责图A步骤②的TRANSACTION-ENDORSED消息收集？

Awesome question—this is a common point of confusion when switching between custom client applications and using the Fabric CLI directly! Let’s break down exactly what’s happening here:

When you run commands like peer chaincode invoke via the Fabric CLI, there’s no standalone client app running in the background—but the CLI itself steps up to fill that role. Here’s how it works:

• The Fabric CLI tool acts as a temporary, lightweight client for your command. It takes on all the client-side responsibilities that a custom application would normally handle, including the step ② task of collecting TRANSACTION-ENDORSED messages from endorsing peers.
• When you execute the invoke command, the CLI first builds the transaction proposal, sends it to the specified endorsing peers, then waits to receive the TRANSACTION-ENDORSED responses from each peer that’s part of the endorsement policy.
• Once it gathers all required endorsement responses, the CLI packages these into a complete transaction payload and sends it to the ordering service for final processing and commit to the ledger—just like a dedicated client application would do.

In short: the CLI doesn’t just fire off the command and exit. It sticks around to manage the full client workflow until the transaction submission is complete.

内容的提问来源于stack exchange，提问作者song chan back