ingokegel opened a new issue, #4010: URL: https://github.com/apache/fory/issues/4010
### Feature Request _No response_ ### Is your feature request related to a problem? Please describe The current behavior is to serialize byte[] to a decimal number array. In my payloads at https://github.com/ej-technologies/serialization-comparison I have measured this to be 4.5× slower and 2.1× larger than base64. This means Jackson JSON is faster than Fory for such payloads. The ecosystem standard for byte arrays in JSON is a base64 string (see RFC 7493). The protobuf JSON mapping, Jackson, Gson, Moshi and kotlinx.serialization all do it that way by default. ### Describe the solution you'd like My proposal is to make Base64ByteArrayCodec the default and the @JsonBase64 annotation to become a no-op. JSON support is still new. While it is a breaking change, its performance impact can be drastic which is an important consideration for Fory. ### Describe alternatives you've considered One could also change the default and make @JsonBase64 more discoverable. But the default would be wrong according to RFC 7493. ### Additional context I will provide a PR. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
