title: Understanding socket names
body: <blockquote>
    <p>Socket names are <strong>strings</strong> and appear in the file system name space through portals.</p>
  </blockquote>
  
  <p>from <a href="http://publib.boulder.ibm.com/infocenter/aix/v7r1/index.jsp?topic=%2Fcom.ibm.aix.progcomm%2Fdoc%2Fprogcomc%2Fskt_comms.htm" rel="nofollow">http://publib.boulder.ibm.com/infocenter/aix/v7r1/index.jsp?topic=%2Fcom.ibm.aix.progcomm%2Fdoc%2Fprogcomc%2Fskt_comms.htm</a></p>
  
  <blockquote>
    <p>The <strong>bind</strong> call is used to assign a name to a socket on the local side of a connection. </p>
  </blockquote>
  
  <p>from <a href="http://osr507doc.sco.com/en/netguide/dusockD.binding_names.html" rel="nofollow">http://osr507doc.sco.com/en/netguide/dusockD.binding_names.html</a></p>
  
  <pre><code>int bind(int socket, const struct sockaddr *address, socklen_t address_len);
  </code></pre>
  
  <p>from the man page of bind.</p>
  
  <p>What EXACTLY are the socket "names"? And do we "set" them? </p>
  
  <p>The bind system call, doesn't seem to have an argument for specifying a name, does it?</p>