From the page "Basic Differences (and similarities) between LIRC and WinLIRC":
LIRC can use both UNIX-domain sockets and TCP/IP sockets for client/server communications. Since UNIX-domain sockets don't exist under Windows, only Internet-domain (TCP/IP) sockets are used. The WinLIRC server listens on TCP port 8765 by default. Client/server communications are otherwise identical (with a few exceptions).
Actually, besides the internet sockets, Windows supports Mailslots and Named Pipes (depending on the features you need) that can be used to replicate a similar behavior of UNIX-domain socket. This kind of platform dependent code, together with the current network based server, would be useful for importing the code of the lirc_client programming interface (nowadays absent because based on AF_UNIX sockets) and for having an alternative way for communicating without the troubles with the network layer or a busy TCP port (for example).
More information may be collected from here:
http://msdn.microsoft.com/en-us/library/windows/desktop/aa365576%28v=vs.85%29.aspx
http://msdn.microsoft.com/en-us/library/windows/desktop/aa365590%28v=vs.85%29.aspx
Assuming this is you :)
http://redmine.audacious-media-player.org/issues/365
I don't think creating domain sockets is the answer here. The problem is Audacious is using the lirc_client.h api. We could probably make a similar lirc_client.h for winlirc with the same API. But they would still need to compile against it for a windows version.