Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:95049 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 58984 invoked from network); 11 Aug 2016 21:59:33 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Aug 2016 21:59:33 -0000 Authentication-Results: pb1.pair.com smtp.mail=dave@mudsite.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=dave@mudsite.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain mudsite.com designates 209.85.217.194 as permitted sender) X-PHP-List-Original-Sender: dave@mudsite.com X-Host-Fingerprint: 209.85.217.194 mail-ua0-f194.google.com Received: from [209.85.217.194] ([209.85.217.194:35994] helo=mail-ua0-f194.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 24/10-56950-345FCA75 for ; Thu, 11 Aug 2016 17:59:32 -0400 Received: by mail-ua0-f194.google.com with SMTP id 74so683950uau.3 for ; Thu, 11 Aug 2016 14:59:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mudsite-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=lgeoFmK9/+FG2PYmKzrprwhUkvpaCjkieQYXXVqRhvg=; b=pExLq3vTN/lhzbMgX4mFCCs4LzmfuSs65Sj0PF9I8sTn3LWFpJQ+ZXr11hIgepcrIW tERJb30qg4618kpQseqDmL/kq/dzGMi30e/PO44TUSh2ronwSNtLcpzl2tfyiaJLwZOg SKfcjbnPfHcURiItYcfHlfHcabq5+EYlZ090+gePlEepszOI8mazV3mjQISmYeibTqF6 pOtoWBIwr74igeNDGfxTh1J4pHeGiz/hEhWhmY6eF2YjWRLnmqb/z9R6NPxkSErOSKwp 5Fo42g5CC6qTY3lBsp9AvsksUPnmvXyODz0vsYvhIECx3+PiOop3LLiSMSgn9VTEUu8Q VxWQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=lgeoFmK9/+FG2PYmKzrprwhUkvpaCjkieQYXXVqRhvg=; b=Hu9wwsvkfZ3fN4Txv5bKCOrXkZx5olBbkhZaJAqLbMffvmwNCOZQfL0FvF4SLfTS3R Eo+5UODdAR0/qOi2oJcYl+tUYzbmEjFi0eP/iodSamc0eRHVy20ZSXOwJGcubpc7trhy n5RzZmCgcHXlHi0xPkDi9dTUwPmEAYhP3JXpddm0HukD5a4A6AXnthuJQTxpGw5a596n lTWh4G3C5jjdQTzDqJc1LI4UUN/gXxFdP6DlDFdjIyPzyR5IOZJw9cYhs3N8zBtSAODR UCYPaLg5INhhJvXuU3JY93uNYrVEOr2Lm0jSk3+5v+NqBbNBkb1eiDBDwiAdCNgHgUUN 6BLQ== X-Gm-Message-State: AEkoouv48BhGqR4ccmFJR6Zst4JcQmXLs2YYO0+F8C7cPGYaYM46io27ZXThHylKKBw99KH0xeZcPE06NDhxqw== X-Received: by 10.176.0.212 with SMTP id 78mr5179522uaj.107.1470952768960; Thu, 11 Aug 2016 14:59:28 -0700 (PDT) MIME-Version: 1.0 Date: Thu, 11 Aug 2016 21:59:18 +0000 Message-ID: To: PHP internals Content-Type: multipart/alternative; boundary=001a113ac77a4696270539d2e12a Subject: Fixing #72733 : Implement getaddrinfo From: dave@mudsite.com (David Walker) --001a113ac77a4696270539d2e12a Content-Type: text/plain; charset=UTF-8 Hi all, I'm looking to resolve this bug, and thought about 2 means in which to implement the request of exposing C's getaddrinfo() and the addrinfo structure. There's not really an equivalent means to accomplish this in userland without trial&error. So I'm not sure the communities best-practices on altering current userland function signatures to implement a new feature. So I've devised 2 means of implementing this feature but don't know which would be preferred. The former introduces new functions for addrinfo-specific usage. The second alters current socket_connect/socket_bind signatures. They are both very similar in their implementation. I'm filling out an RFC[1] for this addition, and have details of each implementation idea typed out in it for you to see what I'm trying. Suggestions and advice on best-practice greatly appreciated. -- Dave [1] - https://wiki.php.net/rfc/socket_getaddrinfo --001a113ac77a4696270539d2e12a--