-
Notifications
You must be signed in to change notification settings - Fork 22
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
Add equivalent of getnameinfo
#3
Comments
Another Pro is that it improves compatibility with existing code that uses this feature. But it still seems relatively niche. What if we include it in the proposal for now, and see how it goes? If we encounter complications, we can remove it. But if it's traighforward, we can just include it, and save ourselves the extra work of discovering applications in the future that eventually need it, and then adding it for them. |
If we were to include |
Yeah, since we have |
Not sure I see the relationship. Despite their unfortunate names,
Ofcourse 😄 Part of the "network" capability or part of some kind of "host info" capability? |
Yeah;
This isn't necessarily definitive, Linux has separate Network and UTS namespaces, so maybe it makes sense to make this a separate "host info" capability. |
Delete files that I included by accident in WebAssembly#2. The real files are named `wasi-proposal-template.*`.
Should the inverse of
resolve_addresses
be part of this proposal? Egresolve_name
based ongetnameinfo
.Although they would be each other's mirror image, their use cases are very different.
resolve_addresses
is used by almost every application that is connected to the internet, while its inverseresolve_name
is relatively niche.The text was updated successfully, but these errors were encountered: