request error enhancement #266
Comments
aricart
added a commit
that referenced
this issue
May 13, 2022
…nders, but in the case of permissions, the client may not be able to publish to the request subject or subscribe to the mux inbox, this change rejects the request providing a more context relevant error. Previously it was only possible to learn about the error due to the async error notification. FIX #266
aricart
added a commit
that referenced
this issue
May 13, 2022
* [FEAT] request API only rejects responses due to timeouts or no responders, but in the case of permissions, the client may not be able to publish to the request subject or subscribe to the mux inbox, this change rejects the request providing a more context-relevant error. Previously it was only possible to learn about the error due to the async error notification. FIX #266
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If a client has pub permission error for the subject of a request, the request will simply come back as having timed out - this is the wrong expedition for the developer - specially if they are not monitoring the status.
on publishing a request we should tag the associated subscription with the request subject, then on handle error we could test the subject to see if was the result of a request and provide a better experience.
The text was updated successfully, but these errors were encountered: