You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar to #268, I also need to manage several client connections at the same time, but instead of load balancing them, I'll be calling them all with something like futures_util::join_all (on a LAN), merging their responses together with their names, and responding the call with this "enriched" answer.
How would I handle errors in this scenario? And timeouts, returning only the answers I could get in time?
Any tips/concerns on making this happen?
Thank you!
The text was updated successfully, but these errors were encountered:
Hi! Sorry for not responding last year. For something like this, I think the Doctors service implementation would be able to implement everything you said pretty straightforwardly: send out N requests with whatever deadline will allow the service to respond in time; iterate over the responses, filtering out any deadline-exceeded errors; and then return the result?
If you're still interested in this and struggling to implement something, feel free to share a link to your work in progress, and I'll try to take a look.
Hi!
Similar to #268, I also need to manage several client connections at the same time, but instead of load balancing them, I'll be calling them all with something like futures_util::join_all (on a LAN), merging their responses together with their names, and responding the call with this "enriched" answer.
So, if I had:
I'd need:
How would I handle errors in this scenario? And timeouts, returning only the answers I could get in time?
Any tips/concerns on making this happen?
Thank you!
The text was updated successfully, but these errors were encountered: