KnowledgeHub
Questions
Tags
Users
Search
Alex Rivera
|
Logout
Edit Question
Title
Body
Is there some subtle reason why java.nio.ByteBuffer does not implement java.io.DataOutput or java.io.DataInput , or did the authors just not choose to do this? It would seem straightforward to map the calls (e.g. putInt() -> writeInt()). The basic problem I (and some others , apparently) have is older classes which know how to serialize/serialize themselves using the generic interfaces: DataInput/DataOutput. I would like to reuse my custom serialization without writing a custom proxy for ByteBuffer.
Tags (comma-separated)
Save Edits
Cancel