http://bugs.winehq.org/show_bug.cgi?id=17316
--- Comment #1 from Rob Shearman robertshearman@gmail.com 2009-02-08 17:15:14 --- It shouldn't matter what transport is used for LRPC, since it is internal to the machine. In theory, it could use UNIX domain sockets instead, but it may be necessary to be able to access the security information of the client (it is currently stubbed) in server code, and so it seems best to keep the implementation as using named pipes so that the work only has to be done once rather than twice.