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
How can I set the timeout for the connect() system call?
What are the pros/cons of select(), non-blocking I/O and SIGIO?
What is active unix domain sockets?
What is a sae socket?
What is sae socket?
Can multiple clients connect to same socket?
What is a socket api?
Are unix sockets faster than tcp?
Why does it take so long to detect that the peer died?
What is a deep well socket?
Why does the sockets buffer fill up sooner than expected?
What is socket address with example?
What pieces of information make up a socket?
Whats the difference between select() and poll()?
Is there any advantage to handling the signal, rather than just ignoring it and checking for the EPIPE error? Are there any useful parameters passed to the signal catching function?
