-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: add Response
class
#1431
Comments
@Lancetnik Can I give this a shot? Could you just brief me a little bit about this? |
@AmanSal1 sorry, I was a little hasty. It's not so easy to implement as I thought. It requires coordinated changes in all publishers, so I'll implement it by myself. If you want to help, you create create a basic |
Could you please check if this is what you meant? For the next part, I suppose we would need to create separate classes for each and inherit the response class for them. Then, we would have to modify the decorator class for each response class |
Yeah, something like this |
@AmanSal1 thank you for the interest! I make a draft release of Response classes, as u can see, but we still need to specify broker-specific options in |
We should create a special class to make users able to setup outgoing message metainformation in
@publihser
decorator caseAlso, the basic case with just a data should be supported as well
More than we should create specific
KafkaResponse
/RabbitResponse
/... classes to allow user to specify broker-specific information like in the following exampleP.S. RMQ ReplyConfig option should be deprecated
The text was updated successfully, but these errors were encountered: