-
Notifications
You must be signed in to change notification settings - Fork 440
Message serialization. #846
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
Conversation
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
@makasim What are we going to do with the PR to queue-interop
? Want me to take over and create a new one?
Honestly, I don't have a good solution. do not know how to properly address it
Honestly, I don't have a good solution. do not know how to properly address it
As discussed in the PR in queue-interop, it has been proposed to drop type for body
parameter in interface. This would open up ability for implementations to handle message serialization on their own 😄
IMO interface is too tight and limits possible approaches. Some transports could actually benefit from this a lot - for example Redis transport can use IGB (don't recall the proper name on top of my head) serialization that is extension-based.
and @makasim I'm only asking since @Sevavietl is currently not responding in queue-interop
PR 😄
Uh oh!
There was an error while loading. Please reload this page.
needs queue-interop/queue-interop#28
initial discussion queue-interop/queue-interop#27
further discussion #831