这是indexloc提供的服务,不要输入任何密码
Skip to content

[Bug]: Unclear specification around message/stream and task/resubscribe #1093

@marianogonzalez

Description

@marianogonzalez

What happened?

Hello... I'm trying to implement an A2A server/client but the behavior around message/stream and task/resubscribe isn't completely clear.

Suppose a client starts a task by calling message/stream but disconnects before it finishes:

  1. When the client reconnects through task/resubscribe, we don't see the spec defining how to specify which was the last received message. If the server to replay the entire thing always?
  2. Now suppose that in between the client disconnecting and resubscribing, the same (or another client) calls message/stream with the same taskId, adding a new message to that task. Are all subscribers expected to get responses from all messages? Or differently put, is the datasource behind task/resubscribe expected to behave as a queue or as topic?

Thanks

Relevant log output

Code of Conduct

  • I agree to follow this project's Code of Conduct

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions