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
At time T5 a client sends another StartRequest to the target; the target is already in the process of handling a previous StartRequest, but not yet in a shutdown state, so it receives the request.
Should it respond with another StartResponse:Success and meaning that the reset is going to happen, or should it send back an gRPC error with a description that explains that another reset request has already been requested?
Hi all,
I would like to discuss what is the right way for a target to handle concurrent Start RPC calls in the scope of a Factory Reset service?
Consider the following call flow
At time T5 a client sends another
StartRequest
to the target; the target is already in the process of handling a previous StartRequest, but not yet in a shutdown state, so it receives the request.Should it respond with another StartResponse:Success and meaning that the reset is going to happen, or should it send back an gRPC error with a description that explains that another reset request has already been requested?
/cc @samribeiro
The text was updated successfully, but these errors were encountered: