On Thu, Oct 27, 2011 at 06:18:30PM +0100, Ramsay Jones wrote: > > It's definitely coming back, so if you feel like working on it, please > > do. Also note that if it would be easier to have an alternate > > abstraction for inter-process communication on windows, I'm open to > > doing that in the cache daemon. > > My initial reaction was to use a "named pipe" (aka fifo), but on reflection, > I don't think it would be any easier; the unix socket emulation should not be too > difficult (famous last words!). :-D The problem with named pipes is that all clients share the same pipe. So if two clients connect, their writes will be intermingled at the server, and they will both get the responses for each other. Assuming your platform provides atomic write() over pipes, you could design a packet-ized protocol, and just have clients ignore packets not meant for them. But that's getting pretty complex. -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html