a2aproject / a2aproject/a2a-java
How does the client record the task IDs that have been sent
Offen
- Vorherrschende Sprache
- Java
- Sterne
- 490
- Forks
- 172
- Ø Merge
- 1 T. 6 Std.
- Gemergte PRs (30 T.)
- 55
Beschreibung
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?
Beitragsleitfaden
Bewertung
Dieses Issue wurde noch nicht bewertet.