Java - Is ObjectInput/OutputStream compatible with DataInput/OutputStream?

Question

For example:

I send a byte[] over Socket outputStream using ObjectInput/OutputStream:

ObjectOutputStream myOutput = new ObjectOutputStream(mySocket.getOutputStream());
myOutput.write(myByteArray);

At the other end, he use DataInputStream (and may use other InputStream as well) to read:

DataInputStream hisInput = new DataInputStream(hisSocket.getInputStream());
hisInput.read(hisByteArray);

So my question is:

Will the receiver read the byte[] correctly?
What about String using writeObject and readUTF?

Info:

I can only use Java library (JRE8) and is new to Java's Stream.
I can not expect or force the other side to use what Stream other than knowing that they are not using ObjectInput/OutputStream
I asked this question because using ObjectInput/OutputStream MAY save me some work, I took advice from my other question.

Just FYI, both the Data and Object Input/Output streams date back to an age when communication/serialization protocols were not nearly as well developed as they are now. These days we have XML and JSON, both of which are technology neutral and big / little endian neutral. — ControlAltDel
– ControlAltDel, Commented Oct 24, 2014 at 15:35

Stephen C · Accepted Answer · 2014-10-24 15:34:12Z

1

Will the receiver read the Byte[] correctly?

No.

What about String using writeObject and readUTF?

No.

If you use ObjectOutputStream.writeObject to write, the only practical way to read the stream is using ObjectOutputStream.readObject.

In theory, you could write code to implement the serialization protocol yourself (using byte or "data" input streams), but it is not a sensible / practical approach.

I can not expect or force the other side to use what Stream other than knowing that they are not using ObjectInput/OutputStream

Whatever you use as the format when you write, you will be forcing the other end to use something that is capable of reading it. Forcing the other end (if it is Java) to use ObjectInputStream should not be a concern. It is another matter if the other end could be implemented in another language, but then you should probably be considering something like JSON or XML as your encoding scheme.

edited Oct 24, 2014 at 15:34

answered Oct 24, 2014 at 15:17

Stephen C

723k95 gold badges849 silver badges1.3k bronze badges

Sign up to request clarification or add additional context in comments.

10 Comments

Tr1et Over a year ago

That's a harsh fact, so in short, ObjectOutputStream can only work with ObjectInputStream????

Stephen C Over a year ago

I didn't say that. I said it is the only practical way. You could implement code that unpicked the Java object serialization format (it is specified!) ... but that is hardly a practical solution.

Tr1et Over a year ago

Java Serialize primitive type too? I thought because it is primitive, it doesn't have to be Serialized.

David Conrad Over a year ago

A Byte[] is not primitive.

Tr1et Over a year ago

@DavidConrad Well, it's related to my other question about forcing or not. But I've edited my question, sorry for my typo, it's actually byte[] not Byte[].

|

Collectives™ on Stack Overflow

Java - Is ObjectInput/OutputStream compatible with DataInput/OutputStream?

1 Answer 1

10 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

10 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related