-
Notifications
You must be signed in to change notification settings - Fork 830
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows AF_UNIX SOCK_DGRAM request #5272
Comments
Good as any (there was some precedent set). |
This would be very helpful indeed 👍 |
For what is worth, missing SOCK_DGRAM support is also the reason why the Python maintainers chose not to expose the unix socket API on Windows [1][2] [1] https://bugs.python.org/issue33408 |
I'm interested in this support as well; I have a library requiring UNIX datagram sockets that currently only works on UNIX, and I'd like to make it work on Windows as well. |
My usecase is this: |
I am also interested in this because it is considered a blocker for exposing the AF_UNIX functionality in Python. Being able to use unix-style sockets would allow me to get rid of a lot of OS-specific python code. |
Also interested in this. Want to build native windows application instead of running it on top of cygwin/msys2. |
Is your feature request related to a problem? Please describe.
Per the blog post announcing AF_UNIX on windows, "Support for the datagram (SOCK_DGRAM) can be considered in future depending on the adoption, feedback and scenarios"
Not sure if it has been asked for elsewhere, but I have a use case where I would find this very helpful
Describe the solution you'd like
The ability to create SOCK_DGRAM AF_UNIX style sockets, thus allowing message boundaries to be preserved
Describe alternatives you've considered
Adding my own basic message boundary headers in a stream socket connection. However, I'd like to be able to plug this into existing libraries that expect datagram sockets without needing to be aware of such a header
Additional context
Note: I am not sure if this is the perfect place to put the request, but https://devblogs.microsoft.com/commandline/af_unix-comes-to-windows/ links to this issue tracker
Thanks!
The text was updated successfully, but these errors were encountered: