tasks/send、tasks/sendSubscribe、Capabilities.stream #398
-
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
As far as I undertand In the A2A protocol, the choice between tasks/send (for short-lived tasks) and tasks/sendSubscribe (for long-running or streaming tasks) is determined by the agentCard.capabilities.stream flag because streaming is a fundamental capability of an agent. If stream is true, it signals that the agent can maintain persistent connections and handle ongoing interactions, so sendSubscribe is used. If false, the agent only supports immediate, one-time responses, 8000 and send is used. This single flag simplifies client logic, ensures consistency, and reflects the agent’s infrastructure capabilities, avoiding the need for multiple capability fields or redundant checks. |
Beta Was this translation helpful? Give feedback.
As far as I undertand In the A2A protocol, the choice between tasks/send (for short-lived tasks) and tasks/sendSubscribe (for long-running or streaming tasks) is determined by the agentCard.capabilities.stream flag because streaming is a fundamental capability of an agent. If stream is true, it signals that the agent can maintain persistent connections and handle ongoing interactions, so sendSubscribe is used. If false, the agent only supports immediate, one-time responses, and send is used. This single flag simplifies client logic, ensures consistency, and reflects the agent’s infrastructure capabilities, avoiding the need for multiple capability fields or redundant checks.