[Question] Why is the method of A2A-python-sdk inconsistent with that of A2A protocol?

[zhangmianhongni]

In the A2A protocol, the A2A client implements the on_send_task method, and the corresponding request path is task/send.

There is a conflict between python-sdk and A2A protocol, I would like to ask, which should be used as the standard? Is it because the SDK is still under development, or will the protocol be modified to message/send?

However, in the current A2A-python project, the A2A client implements the on_send_message method, and the corresponding request path is message/send.

[Abiorh001]

i also asked same question in the main A2A repo i feel like its should be on_send_task not on_send_message because any message thats send my host agent to remote agent is classified as a task

[graphnj]

Same question.
I check/review specification/json/a2a.json it's still "tasks/send" and "tasks/sendSubscribe"

[holtskinner]

The protocol has been updated, and the SDK hasn't included this change yet. @kthota-g for context

[kthota-g]

Hi,
The SDK is implementing the upcoming version of the protocol and so the changes.

Updates to the protocol are being merged into next branch here - https://github.com/google/A2A/tree/next. This is still wip and there are a few outstanding PRs currently.

Here is the PR that describes the method name changes - a2aproject/A2A@b970815

[holtskinner]

This should be updated in the latest version of the SDK