title: FastCGI on port vs. on socket
body: <p>I was setting up Django on Cherokee today (using SCGI), and I noticed that <a href="http://docs.djangoproject.com/en/dev/howto/deployment/fastcgi/" rel="noreferrer">the Django docs</a> say that you can use either a host/port combination or a socket for communication between the webserver and Django.</p>
  
  <p>The only thing they have to say on the matter is</p>
  
  <blockquote>
    <p>What you choose is a manner of preference; a TCP socket is usually easier due to permissions issues.</p>
  </blockquote>
  
  <p>(Incidentally, I've had permissions problems with doing this with a socket, but not with a host :). )</p>
  
  <p>I vaguely remember how sockets work from my systems programming class, but I'm really curious as to what the effective difference is between the two.  Any time there's a choice of something, there's <em>someone</em> with an opinion on the matter, so I was hoping to get that.  In particular, is there any performance difference?</p>
  
  <p>Or, if it really doesn't matter at all, I'd just like some confirmation, so I can continue on with my programming and ignore this sysadmin-y stuff.</p>