title: Sockets vs named pipes for local IPC on Windows?
body: <p>Are there any reasons for favoring named pipes over sockets for local IPC (both using win-api), effectiveness-wize, resource-wize or otherwise, since both behave very much alike (and likely to be abstracted by a similiar interface anyway), in an application that is likely to already use sockets for network purposes anyway?</p>
  
  <p>I can name at least the addressing issue: port numbers for sockets against filenames for pipes. Also, named pipes (AFAIK) won't alert the firewall (block/unblock dialog), although blocked applications can still communicate via sockets locally. Anything else to take into account?</p>
  
  <p>In the case of using sockets, are there any winsock settings/flags that are recomended when using sockets locally?</p>