You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.
With v5.0 came the support for Unix Domain Sockets for http servers. As far as I know these only work on Unix systems, where UDSs are natively supported. When I try to listen to a socket on Windows, I get an EACCESS error, no matter what I do.
Would it be possible to use Sockets on Windows too using the Winsock API? Maybe either Node.js or libuv could abstract them to a common interface.
Thoughts?
The text was updated successfully, but these errors were encountered:
I can be more specific. If you name the pipe 'echo.sock' you get an eacces error. I looked in common.js referred to above and used the name in there and it worked. Some documentation about what names are legal would be helpful. Or, maybe some kind of function to make named pipes universal across systems, e.g.,
With v5.0 came the support for Unix Domain Sockets for http servers. As far as I know these only work on Unix systems, where UDSs are natively supported. When I try to listen to a socket on Windows, I get an
EACCESS
error, no matter what I do.Would it be possible to use Sockets on Windows too using the Winsock API? Maybe either Node.js or libuv could abstract them to a common interface.
Thoughts?
The text was updated successfully, but these errors were encountered: