Matthew Pope
Matthew Pope
Thanks for bringing this to our attention. We'll need to understand the ramifications before we make any changes—I'll be the first to admit that I am only familiar with Java...
> I'm currently cinsuming ion-java as a transitive dependency of com.amazonaws:aws-java-sdk-s3:$1.12.374 So are you actually using Ion in your application, or are you only dealing with this issue because it's...
The last time I spoke with the people responsible for the AWS Java SDK, they told me that Ion is not actually supported by the SDK. Since it's apparently not...
Hi @Marcono1234, Thank you for bringing this up, and I'm sorry that it has taken this long to get back to you. We can certainly update all of the `http`...
Thank you. We will look into this.
@Marcono1234, thanks for your patience with this. As you can probably guess, some of these changes require some work behind closed doors with our security teams and from the outside...
> Valid encodings are UTF-8, UTF-16, and UTF-32 for text encoded Ion. Binary encoded Ion must not specific a charset. The default charset value is UTF-8. > > **Encoding considerations:**...
Now that I've looked a little closer, I think you're right.
If we remove the feature gate for `Encoding`, then we need to add a feature gate specifically to the Ion 1.1 encodings (until the Ion 1.1 spec is finalized). Currently,...
I did some experimentation on this, and here is what I discovered: * Currently, the RawBinaryReader implementations expose byte offsets for annotations and the actual value. That should be enough...