Replies: 1 comment
-
We are exploring a bit, we would not use the encoded conns and more likely would introduce a better way of chaining handlers together, similar to "middleware" for HTTP. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Is there any plan to upgrade to go 1.18 so that generics can be introduced for Encoded Connections? That allows for a generic Request function that would be more convenient to use.
I would like create a pull request for a version that I modified and I added a few functionalities for Encoded Connections which require go 1.18
1- A generic version of
Request
which returns a wrapped result underEncodedMsg
2- I added
Headers
to the newEncodedMsg
struct3- I added another version of
Publish
to acceptEncodedMsg
so that headers could be used as wellI required these features, because I would like to somehow deliver a response when something goes wrong in the subscriber and a response cannot be produced. Then I can report the error through headers. But the existing version does not allow that. (Headers are available for plain connections and not encoded connections)
Beta Was this translation helpful? Give feedback.
All reactions