Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95432
Return-Path: <derick@php.net>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 90944 invoked from network); 24 Aug 2016 15:58:12 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 24 Aug 2016 15:58:12 -0000
Authentication-Results: pb1.pair.com smtp.mail=derick@php.net; spf=unknown; sender-id=unknown
Authentication-Results: pb1.pair.com header.from=derick@php.net; sender-id=unknown
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 82.113.146.227 as permitted sender)
X-PHP-List-Original-Sender: derick@php.net
X-Host-Fingerprint: 82.113.146.227 xdebug.org  
Received: from [82.113.146.227] ([82.113.146.227:50312] helo=xdebug.org)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 37/0A-10212-214CDB75 for <internals@lists.php.net>; Wed, 24 Aug 2016 11:58:11 -0400
Received: from localhost (localhost [IPv6:::1])
	by xdebug.org (Postfix) with ESMTPS id 4171310C01C;
	Wed, 24 Aug 2016 16:58:07 +0100 (BST)
Date: Wed, 24 Aug 2016 16:58:06 +0100 (BST)
X-X-Sender: derick@whisky.home.derickrethans.nl
To: David Walker <dave@mudsite.com>
cc: PHP internals <internals@lists.php.net>
In-Reply-To: <CADVQu1SUyRa3GsUDMNu2WLJhDg_Trp7u-KycZmHRUjYTMX-B9A@mail.gmail.com>
Message-ID: <alpine.DEB.2.20.1608241655280.14616@whisky.home.derickrethans.nl>
References: <CADVQu1SUyRa3GsUDMNu2WLJhDg_Trp7u-KycZmHRUjYTMX-B9A@mail.gmail.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Subject: Re: [PHP-DEV] [RFC][VOTE]: Implement socket_getaddrinfo family
From: derick@php.net (Derick Rethans)

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 reason why addrinfo is a 
resource, and not an object? I realize resources are needed for the 
actual socket, but is it needed for the addrinfo information?

I would also like to see (in the RFC, but certainly in the docs), how 
this works connecting to a specific IPv6 address resource.

cheers,
Derick