You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thank you for your amazing work done.
The java library is not compatible with the dotnet library and others since the java namespace is located inside a dynamic array raol/amazon-sqs-net-extended-client-lib#32.
In golang, the library tends to support the latest version but still, previous java library with other namespace is not compatible when the golang client sends a sqs message to a java consumer. Here is an attempt which is not compatible with older java versions: https://github.com/jwcorle/sqs-extended-client-go/blob/main/client.go#L201
I find that putting such namespace is annoying, how about using only the pointer with the bucketname and the s3key like in dotnet and golang
The text was updated successfully, but these errors were encountered:
Hi!
First of all, thank you for your amazing work done.
The java library is not compatible with the dotnet library and others since the java namespace is located inside a dynamic array raol/amazon-sqs-net-extended-client-lib#32.
In golang, the library tends to support the latest version but still, previous java library with other namespace is not compatible when the golang client sends a sqs message to a java consumer. Here is an attempt which is not compatible with older java versions: https://github.com/jwcorle/sqs-extended-client-go/blob/main/client.go#L201
I find that putting such namespace is annoying, how about using only the pointer with the bucketname and the s3key like in dotnet and golang
The text was updated successfully, but these errors were encountered: