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
I was just wondering if it makes sense to add a similar functionality to that of python'ssocketmodule to this crate so the hostname (FQDN or not) of the machine (for the local end of) socket is returned? or this is something beyond/unrelated to this crate?
The text was updated successfully, but these errors were encountered:
any hints/directions on design of the API is appreciated. For example, should we support gethostnmame() for all possible combination of Domain, Type and Protocol that socket2 offers or just focus on some?
(ex: does adgram type unix-domain socket need to have access to gethostname())
I was just wondering if it makes sense to add a similar functionality to that of python's
socket
module to this crate so the hostname (FQDN or not) of the machine (for the local end of)socket
is returned? or this is something beyond/unrelated to this crate?The text was updated successfully, but these errors were encountered: