[THRIFT-449] The wire format of the JSON Protocol may not always be valid JSON if it contains non-UTF8 encoded strings

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 0.1
• Fix Version/s: 0.10.0
• Assignee: Jake Farrell
• Reporter: Chad Walters
• Created: 10/Apr/09 00:12
• Updated: 06/Jan/16 02:16
• Resolved: 06/Jan/16 02:16

Description

Valid JSON is always Unicode. The JSONProtocol does not always have a wire format that conforms to this – strings that are not UTF8 encoded can end up writing bytes into the transport that are not valid UTF8.

I am trying to come up with a way to handle this that doesn't entail escaping every byte above 0x7F into a 6 byte escape sequence "\uXXXX". Suggestions welcomed.