I've been interested in this for a while https://github.com/softprops/hyperlocal … . The azure team forked this for windows https://github.com/Azure/hyperlocal-windows … it's on my list to backport to windows support to hyperlocal proper
-
-
-
Ohhh!
End of conversation
New conversation -
-
-
the node `net` module supports both unix domain sockets and windows named pipes so probably not too different. i don't actually know what the differences are and have not run into a reason to think about that, the one or two times i've used them…
-
Interestinggg!
End of conversation
New conversation -
-
-
net.connect/tls.connect in Node support both with the same interface: https://nodejs.org/api/net.html#net_net_connect … I added support for both Unix Domain Sockets and Windows Named Pipes in Autocannon using this api: https://github.com/mcollina/autocannon/blob/798df79e96871a0f841cde2a73e1aa67cccae958/lib/httpClient.js#L106 …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
The big problem is that you don't control where named pipes land on disk. Consuming named pipes if you have a handle on them is simpler than making an abstraction that makes sense due to pathing diffs.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Unix sockets (AF_UNIX) can be message based too, not just SOCK_STREAM(tcp)! http://man7.org/linux/man-pages/man2/socket.2.html …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.