Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95429
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.43 as permitted sender)
MIME-Version: 1.0
Reply-To: bishop@php.net
Sender: bishop.bettini@gmail.com
In-Reply-To: <CADVQu1SUyRa3GsUDMNu2WLJhDg_Trp7u-KycZmHRUjYTMX-B9A@mail.gmail.com>
References: <CADVQu1SUyRa3GsUDMNu2WLJhDg_Trp7u-KycZmHRUjYTMX-B9A@mail.gmail.com>
Date: Wed, 24 Aug 2016 11:47:32 -0400
Message-ID: <CAEYWF=46kT0_GGcCA66JmVngHHEG=PRwkPGN2Sa=VP-KTut0jQ@mail.gmail.com>
To: David Walker <dave@mudsite.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a113c51c6d8062f053ad3345e
Subject: Re: [PHP-DEV] [RFC][VOTE]: Implement socket_getaddrinfo family
From: bishop@php.net (Bishop Bettini)

--001a113c51c6d8062f053ad3345e
Content-Type: text/plain; charset=UTF-8

On Wed, Aug 24, 2016 at 11:26 AM, David Walker <dave@mudsite.com> 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 lookups.

Would you please add example usage and output of socket_addrinfo_explain to
the RFC, as that'll drive documentation creation?

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).

--001a113c51c6d8062f053ad3345e--