handle tasks/resubscribe with multiple active stream/message

[adsri]

I have a use case where user wants to run multiple stream/message for a given taskId, if one of the stream/message requires reconnection , how to do that. currently we resubscribe on taskId, so it will start providing events for all the different streams.

[darrelmiller]

@adsri Events are not tied to streams. The events are related to what is happening to the task. If you sent multiple messages to a single task and have multiple open streams, I would expect you to get the same set of events on each stream. Are you seeing something in the specification that suggests otherwise?

[adsri]

Thanks for the reply @darrelmiller , specification donot mention anything around how we handle the stream responses. My use case is something like this:

User have a set of messages part of same task and they want to process in parallel and get responses as streams for it.

When all connections are intact each individual stream connection is receiving the response from the task for that particular message request but when any reconnection happens , user calls task/resubscribe using taskId instead of a individual messageId as per the specification due to this now all the messages across the different messageId streams gets handled in the single task/resubscribe even though only one of the stream is reconnecting.

Question: I want to understand what is the recommended way we should handle this scenario and also are we thinking of including messageId as well for the task/resubscribe ?

Also around each message stream receives events from different stream request as well, I think it will make prediction of responses and handling a bit difficult on client side, as Events across all different streams are getting handled even though user expect response for a individual message

Let me know if my understanding is not correct and o should handle responses differently

[darrelmiller]

@adsri An agent may be able to process multiple incoming messages in parallel, but the events returned from a task are correlated to the task and not to any particular message. You may be able to create an extension that allows the resubscribe method to include metadata that causes the stream to only return artifact events that the agent correlates to a particular message, but a task has only one status value, so you wouldn't be able to filter status events.
By default all streams return all events for the task. I do not expect that to change in the default protocol. For your scenario I would highly recommend considering having one task per message and using the relatedTask mechanism to group them.