Why doesn't OutputStream.write() return an int?

[Daniel]

Does anyone know if there's a way to determine how many bytes actually
were written to the underlying stream?

As you may know, OutputStream.write doesn't return an int, but is
declared void. Especially for Sockets, it would be interesting to see
how many bytes actully were written. I know that's in the hands of the
underlying TCP implementation and other buffers, but can I be certain
that when the thread returns from OutputStream.write(), that the data
was or will be written to the socket if no exceptions are thrown after
flushing the stream?



Thanks,
Daniel.

 

[Illya Kysil]

Hello, Daniel!
You wrote on 26 Nov 2003 16:26:22 +0100:

D> Does anyone know if there's a way to determine how many bytes actually were written to
D> the underlying stream?

D> As you may know, OutputStream.write doesn't return an int, but is declared void.
D> Especially for Sockets, it would be interesting to see how many bytes actully were
D> written. I know that's in the hands of the underlying TCP implementation and other
D> buffers, but can I be certain that when the thread returns from OutputStream.write(),
D> that the data was or will be written to the socket if no exceptions are thrown after
D> flushing the stream?
java.iutputStream.write writes ALL passed data to underlying stream and/or OS buffers.
Otherwise it throws an exception.

Yes, data will be written. But that doesn't imply that it will be transmitted.
AFAIK the only value you can trust is the number of bytes other side received...

Regards
Illya Kysil, software developer
Delphi/C/C++/C#/Java/Forth/Assembler
If it is NOT SOURCE, it is NOT SOFTWARE. (C) NASA