How do Sockets Work?
Answer / 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 |
What is the difference between a socket and a port?
What does af mean in sockets?
When should I use UDP instead of TCP?
Why do I get EPROTO from read()?
How do I send [this] over a socket?
What is the difference between SO_REUSEADDR and SO_REUSEPORT?
Why sockets are used?
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?
What is the difference between read() and recv()?
How are unix domain sockets implemented?
system choose one for me on the connect() call? Should I bind() a port number in my client program, or let the?
How does unix socket work?