Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95105
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain mudsite.com designates 209.85.217.173 as permitted sender)
MIME-Version: 1.0
References: <CADVQu1Qq5_ftiT38Sc0jr030KubBZASnpJicxLSZrY3psz4f+w@mail.gmail.com>
 <CAEYWF=4qLiCsecySYY-i_0AT6V8sujaanEi93RC0VP+6OSUzFw@mail.gmail.com>
In-Reply-To: <CAEYWF=4qLiCsecySYY-i_0AT6V8sujaanEi93RC0VP+6OSUzFw@mail.gmail.com>
Date: Fri, 12 Aug 2016 22:04:58 +0000
Message-ID: <CADVQu1QM1SmB8nGFc7TwhcsO15fMyq3XLGyqJe==vdrncipqcA@mail.gmail.com>
To: PHP internals <internals@lists.php.net>, bishop@php.net
Content-Type: multipart/alternative; boundary=94eb2c097a385d2ed20539e71308
Subject: Re: [PHP-DEV][RFC] Fixing #72733 : Implement getaddrinfo
From: dave@mudsite.com (David Walker)

--94eb2c097a385d2ed20539e71308
Content-Type: text/plain; charset=UTF-8

On Thu, Aug 11, 2016 at 6:50 PM Bishop Bettini <bishop@php.net> wrote:

> I feel the weight of new functions, but really getaddrinfo is meant to
> both simplify and unify how sockets are dealt with in the modern era.
> socket_getaddrinfo converts the returned linked list into an array of,
> essentially, socket contexts. The user can inspect those contexts and
> choose the one he wants to use in connect and bind. Simple.
>
> With a few minor tweaks to naming (to lump all the addrinfo functions
> together), this makes sense to me:
>
> $contexts = socket_addrinfo_lookup($node, $service, $hints);
> foreach ($contexts as $context) {
>     print_r(socket_addrinfo_explain($context));
> }
> $socket = socket_addrinfo_connect($contexts[1]);
> // ...
>
> So I would lean toward flavor #1. Thanks!
>


 Bishop,

Thanks, I was really thinking that #1 would be preferred over altering
argument types to long-existing functions.  I have updated the RFC to
include only it's implementation as well as changed the function names.

--
Dave

--94eb2c097a385d2ed20539e71308--