Skip to content
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

Some transports may need to access information about serialization and encoding #7222

Open
mauroservienti opened this issue Nov 19, 2024 · 0 comments

Comments

@mauroservienti
Copy link
Member

Describe the suggested improvement

Is your improvement related to a problem? Please describe.

As described by Particular/NServiceBus.AmazonSQS#2630, the Amazon SQS transport currently doesn't support binary serialized messages. That is due to the underlying infrastructure wire format and how the transport handles native integration scenarios.

Describe the suggested solution

It would be handy if the transport could know the serialization format or the message serialization encoding to handle the various native integration scenarios better.

Additional Context

No response

@kentdr kentdr changed the title Some transport may need to access information about serialization and encoding Some transports may need to access information about serialization and encoding Nov 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant