Input Stream Shutdown and different platforms

Hi,

I am reading a book about sockets and in one particular section it talks about input shutdown. However it says that the input shutdown woerks differently on BSD platform, Winsock platform and Linux platform.

For example it says that closing the input stream on a BSD platform would still allow the remote client to send data without any exception being returned (that is the remote end point still can send the data and no exception is returned even though the input stream is closed). On the other hand closing the input stream on a Winsock platform would make the remote client get an EOFException.

So does this mean that Sockets in Java are implemented differently depending on the system deployed?

Also does this different have any potential effect on the design of a socket based application?

Just another further question. When we talk about Winsock platform, we mean windows right?

Thanks and Regards,

Sim085

[969 byte] By [sim085a] at [2007-11-27 4:54:29]
# 1

Sounds like my book.

> So does this mean that Sockets in Java are

> implemented differently depending on the system

> deployed?

It means that socket input-shutdown is implemented differently in the platforms themselves. Nothing to do with Java.

> Also does this different have any potential effect on

> the design of a socket based application?

Obviously. However practically nobody uses input shutdown so it's not really a concern.

> Just another further question. When we talk about

> Winsock platform, we mean windows right?

Yep. WINSOCK is the name of the interface specification used on Windows by applications for socket programming.

ejpa at 2007-7-12 10:09:10 > top of Java-index,Core,Core APIs...
# 2

> Sounds like my book.

Indeed it is ... altough I am sure you already heared such good comments, I must say it is really a good book :) I have just started reading the book and already learnt a lot on sockets in java then what I already knew!

> > So does this mean that Sockets in Java are

> > implemented differently depending on the system

> > deployed?

>

> It means that socket input-shutdown is implemented

> differently in the platforms themselves. Nothing to

> do with Java.

ok

> > Also does this different have any potential effect on

> > the design of a socket based application?

>

> Obviously. However practically nobody uses input

> shutdown so it's not really a concern.

ok

> > Just another further question. When we talk about

> > Winsock platform, we mean windows right?

>

> Yep. WINSOCK is the name of the interface

> specification used on Windows by applications for

> socket programming.

Ok, I understand. At the beginning of the book I thought that WINSOCK referred to the Sockets implementation in .Net since I remember using such a component in one of my school projects. However when I arrived at this section I saw it being compared more with BSD and Linux implementation and thus it made it more understandable to what WINSOCK referred to. I never would have thought however that different operating systems would implement the TCP standard differently.

Thanks for the replies and the book ?it is really helping me out in understanding Sockets more clearly :)

Regards,

Sim085

sim085a at 2007-7-12 10:09:10 > top of Java-index,Core,Core APIs...
# 3
> I never would have thought however that different> operating systems would implement the TCP standard differently. Neither would I ;-)
ejpa at 2007-7-12 10:09:10 > top of Java-index,Core,Core APIs...