[THRIFT-830] Switch binary field implementation from byte[] to ByteBuffer

• Type: Sub-task
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 0.4
• Component/s: Java - Compiler, Java - Library
• Assignee: Bryan Duxbury
• Reporter: Bryan Duxbury
• Created: 26/Jul/10 22:18
• Updated: 08/Jan/15 13:58
• Resolved: 06/Aug/10 00:20

Description

Instead of using byte[] as the implementation for binary fields, let's use ByteBuffer.

There's nothing that you can do with byte[] that you can't also do with ByteBuffer, and there are more things you can do with ByteBuffer. It opens the way for us to avoid needless buffer copies on serialization and deserialization. It gives us a generally accepted equals() and compareTo() implementation, so we don't have to have custom cases for that anymore.

Making this change will probably cause more than a little bit of trauma, changing the method signatures in both TProtocol and generated code. It's possible that I could be persuaded to support a command line switch for producing old-style byte[] methods in some contexts, but I'd love not to waste time supporting suboptimal features.

Issue Links

• incorporates: THRIFT-226 Collections with binary keys or values break equals()