Answer Posted / chaitanya
The implementation is left up to the vendor of your particular unix, but from the point of view of the programmer, connection-oriented sockets work a lot like files, or pipes. The most noticeable difference, once you have your file descriptor is that read() or write() calls may actually read or write fewer bytes than requested. If this happens, then you will have to make a second call for the rest of the data. There are examples of this in the source code that accompanies the faq.
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
What is a socket file?
What is a socket set used for?
Why do we need socket programming?
How do I convert a string into an internet address?
Can multiple clients connect to same socket?
How many sockets can a port have?
What is a socket api?
Why does it take so long to detect that the peer died?
What are the pros/cons of select(), non-blocking I/O and SIGIO?
system choose one for me on the connect() call? Should I bind() a port number in my client program, or let the?
Why do we need sockets?
What does af mean in sockets?
Why do I get EPROTO from read()?
Is a socket a file?
What is difference between socket () and serversocket () class?