How does the client record the task IDs that have been sent

Open
#909 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
api, backend

Research direction

Look at the SSE client connection and subscription handling code in the SDK. Identify where task IDs are generated and sent. Research best practices for reconnection and state persistence in SSE clients. The solution likely involves modifying the client to store and retrieve subscription IDs, possibly in a local cache or persistent storage.

Written by the indexing model from the issue text.

Description

There is a scenario where the client initiates event subscription to the server and maintains a long connection through SSE. When the SSE is disconnected due to network fluctuations, the client needs to re-subscribe.

But at this point, how can the client know the task ID of the subscription?

Can it only be achieved by persisting the context ID or the task ID?

What should the best practices be like?

Dominant language
Java
Stars
514
Forks
200
Avg merge
1d 2h
Merged PRs (30d)
53

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from a2aproject/a2a-java

All issues in a2aproject/a2a-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.