I'm developping a C application that make extensive use of sockets.

My doubt is: Does every socket that I create have its own buffers to send and/or receive messages from other sockets?

In other words, can sockets be influenced by messages exchange erroneously?

By erroneously I mean without the explicit code (including also the code written by mistake) that makes messages for one socket accessible to other sockets?

I'm developping a C application that make extensive use of sockets.

My doubt is: Does every socket that I create have its own buffers to send and/or receive messages from other sockets?

In other words, can sockets be influenced by messages exchange erroneously?

By erroneously I mean that messages sent to one socket can be "leaked" to another socket without having written (and be it by mistake) program code that would explicitly transmit messages from the "intended" receiver to another socket.

I was wandering wheter ask this question here or on Stack Overflow but it seems to me that this section is more appropriate. I'm developping a C application that make extensive use of sockets. My doubt is: Does every socket that I create have its own buffers to send and/or receive messages from other sockets? In other words, can sockets be influenced by messages exchange erroneously? By erroneously I mean without the explicit code (including also the code written for mistake) that makes them exchange messages?

I'm developping a C application that make extensive use of sockets. 

My doubt is: Does every socket that I create have its own buffers to send and/or receive messages from other sockets? 

In other words, can sockets be influenced by messages exchange erroneously? 

By erroneously I mean without the explicit code (including also the code written by mistake) that makes messages for one socket accessible to other sockets?