Re: [naviserver-devel] nsproxy module: change comm to sockets instead of pipes?

[Stephen D. <sd...@gm...>]

On Sat, Jan 28, 2012 at 8:19 PM, Ibrahim Tannir <it...@ar...> wrote:
>
> However, the entire asynchronous IO in Windows is really messy
> business, since the entire mechanism of processing IO
> notifications is tied to a window.

I see what y'all mean. That's a lot of non-shared code.

I suppose you can always use a unix domain socket on the unixy side
while using a socket on the loopback interface for Windows and still
use the same poll() code on both.