[Windows] concurrent client connections on a named pipe fail

[simonferquel]

If 2 clients running in parallel try to connect to Datakit at the same time, there is a chance that one of them fail with a connection timeout.

This might be due to the fact that their should be a pool of server socket waiting for clients on the same named pipe at any time (and not a single awaiter in a loop).

[samoht]

Is that supported? I remember @djs55 saying that this protocol was a bit weird.

[simonferquel]

That is the way I ususally do named pipe servers on Windows

[talex5]

@djs55 Do we need to change something in our named pipe support on Windows to fix this?