-
Named pipes is a great way to communicate on Windows, but provides issues when wanting to forward/reroute or even debug on Windows. Tools like Thunder/Postman do not support the use of Named Pipes.
-
AF_UNIX has been available on Windows since 2017 (https://devblogs.microsoft.com/commandline/af_unix-comes-to-windows/).
Can we use Unix sockets instead of named pipes on Windows?
-
I'm only interested in omake at the moment. I want to compile omake in Cygwin and have it work in this POSIX environment.
ghost updated
3 months ago
-
Why do we need to communicate like this?
Pytest reports tests as it discovers/runs it. we moved to this model so User has feedback on what is going on. For repos with > 10k tests some times the disco…
-
Split from https://github.com/mvdan/sh/issues/513, since this one can be reproduced by @theclapp on his Mac machine.
It doesn't seem to be the same issue that we're seeing with pseudo-TTYs on CI, w…
mvdan updated
2 years ago
-
TCP sockets on localhost run the risk that untrusted code running on the same machine (under a different user) could connect to the system. Windows named pipes or Unix domain sockets should be used i…
-
For local, interprocess comms, that do not go outside the machine, it would be nice to have a named pipes transport that can be used. Named pipes is supported with .net standard 2.0, so it could be do…
-
```
Reading about local IPC on Windows leads me to idea that Named Pipes is not the
transport should be used where Unix Domain sockets are on Unix. Other, most
probably faster, should be.
ALPC and U…
-
```
Reading about local IPC on Windows leads me to idea that Named Pipes is not the
transport should be used where Unix Domain sockets are on Unix. Other, most
probably faster, should be.
ALPC and U…
-
This bug report is not really satisfying because I don't know how to obtain more informations. I'm using `Rpc.Connection.create` on a reader and a writer created from named pipe, fifo [[1](https://git…
bobot updated
4 years ago