On Wed, Aug 24, 2016 at 9:48 AM Bishop Bettini wrote:
> Also, it may be beneficial to elaborate on the scenarios where
>> socket_addrinfo is easier to use than socket_* and friends (getservbyname
>> for example) and the costs of that ease (eg, behind the scenes DNS queries).
>
>
Most of the get*b
On Wed, Aug 24, 2016 at 9:58 AM Derick Rethans wrote:
> On Wed, 24 Aug 2016, David Walker wrote:
>
> > I'd like to open voting on my RFC[1] to implement getaddrinfo(). The
> > RFC implements 4 new socket extension functions to aid in the calling,
> > examining, and connect/binding of the addrinf
On Wed, 24 Aug 2016, David Walker wrote:
> I'd like to open voting on my RFC[1] to implement getaddrinfo(). The
> RFC implements 4 new socket extension functions to aid in the calling,
> examining, and connect/binding of the addrinfo structure.
Sorry, I missed this discussion. Is there a reaso
On Wed, Aug 24, 2016 at 11:26 AM, David Walker wrote:
> I'd like to open voting on my RFC[1] to implement getaddrinfo(). The RFC
> implements 4 new socket extension functions to aid in the calling,
> examining, and connect/binding of the addrinfo structure.
>
+1 from me -- let the OS do the loo
Hi,
I'd like to open voting on my RFC[1] to implement getaddrinfo(). The RFC
implements 4 new socket extension functions to aid in the calling,
examining, and connect/binding of the addrinfo structure.
--
Dave
[1] - https://wiki.php.net/rfc/socket_getaddrinfo
