Hello guys
Hello guys,
Now UTF8String is supported on all platforms,
10 Seattle`s TJSONReader and TJSONWriter implementation could rely on UTF8String instead of UnicodeString?
UTF8String could lead to a lot of memory usage gains.
From JSON RFC:
"JSON text SHALL be encoded in UTF-8, UTF-16, or UTF-32. The default encoding is UTF-8, and JSON texts that are encoded in UTF-8 are interoperable in the sense that they will be read successfully by the maximum number of implementations."
Thanks :D
Now UTF8String is supported on all platforms,
10 Seattle`s TJSONReader and TJSONWriter implementation could rely on UTF8String instead of UnicodeString?
UTF8String could lead to a lot of memory usage gains.
From JSON RFC:
"JSON text SHALL be encoded in UTF-8, UTF-16, or UTF-32. The default encoding is UTF-8, and JSON texts that are encoded in UTF-8 are interoperable in the sense that they will be read successfully by the maximum number of implementations."
Thanks :D
I think the internal implementation of TJSON* doesn't matter so much. What matters is how the final json string is encoded or how the input json string is decoded.
ReplyDelete