Newsgroups: php.internals,php.pecl.dev Path: news.php.net Xref: news.php.net php.internals:102375 php.pecl.dev:15375 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 95549 invoked from network); 22 Jun 2018 22:40:34 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Jun 2018 22:40:34 -0000 Authentication-Results: pb1.pair.com header.from=rowan.collins@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=rowan.collins@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.128.181 as permitted sender) X-PHP-List-Original-Sender: rowan.collins@gmail.com X-Host-Fingerprint: 209.85.128.181 mail-wr0-f181.google.com Received: from [209.85.128.181] ([209.85.128.181:32964] helo=mail-wr0-f181.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 38/81-32156-FDA7D2B5 for ; Fri, 22 Jun 2018 18:40:32 -0400 Received: by mail-wr0-f181.google.com with SMTP id k16-v6so8077890wro.0; Fri, 22 Jun 2018 15:40:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:subject:to:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=CXZr14kegt90TFV74haHjhodIYed3dFV6f8G403pijk=; b=XpkcVpWE2s/yv3PnJ7vUHMbB+kdHBDMA71VozaeFMRhNTYxwnFddL/gY1u39325w72 5VC9qTeOcSGOs4lR0eX/PJp7GOMT/wkkjgdj7O9l1bs0oBz6Z/aD4ztbtK5mSS/5UjfT USO6LST3Ru+/OSaDaqufZDhXx0FXkHBYgnFnUohcHm4K/yT9TFWXa8yYGwbodsEXKN2x k+eQBMzXVOn49XGpMybhzJ+AZTg2oO8a4BlUizY2wteC/jmtZ5/A+kxooUaVzRSOk8vu hWQp9Vzfwr47PIFo2YkkNNqgqgvwcT7BcGpNdbkBhtb2mADm8V4iGyWcfTMSVRlRiMx3 spKg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=CXZr14kegt90TFV74haHjhodIYed3dFV6f8G403pijk=; b=Vq4Dfzdme4bHDI0xA9itSco0pSbt5eHF7cgjgWgicExzQRvdc27y9SmnDNw6Gsu0fu 4KPXEnnQY1pKRWXw/iojZP10c6oLEDY4M0TOscdLx702NCzJK1uJ4NjhpExTwWvFzwCv Rgj0yqCcxIJt/4nVJ+S875EqV/HhDPeuWdIc9ns/KE4zjCCnnIGZq8qLs0mqe6ufAZ4s sjO5w27IYnhtLZKsGrwD3WOQNkj05p9ThTVmBs5vVjLZTFSGVtQS454nv+0DE6YWaIz/ HAH7KyeqygFZ5wgf+1PznWUOsx8HwDCnk63L1yTrJ0kLMtoJvGgWonxAGdYDu91gqGy+ VYgg== X-Gm-Message-State: APt69E0sd9JDp2fMQpwkPAnAp1rmAlrMsUS4Gpr28xUAUR6RPyieO3E7 OT2rXdOOBnjTdFL61pvPkpn7OroS X-Google-Smtp-Source: AAOMgpemrGJP9wy03/OQZW8eoc2y1qdcT+euHtDdlQGNWl2jLfyJIShlq0V6Y6BE6pc+63KhAXIPSA== X-Received: by 2002:adf:8701:: with SMTP id a1-v6mr3162078wra.178.1529707229263; Fri, 22 Jun 2018 15:40:29 -0700 (PDT) Received: from ?IPv6:2a00:23c4:4b86:4b00:572:2c16:cf9b:6c84? ([2a00:23c4:4b86:4b00:572:2c16:cf9b:6c84]) by smtp.googlemail.com with ESMTPSA id k82-v6sm5687848wmg.10.2018.06.22.15.40.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 22 Jun 2018 15:40:28 -0700 (PDT) To: pecl-dev@lists.php.net, PHP Internals Message-ID: Date: Fri, 22 Jun 2018 23:40:27 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB Subject: memcache, without a d, as in Venezuela From: rowan.collins@gmail.com (Rowan Collins) Hi all, (Cross-posting to PECL and Internals lists, because I'm not sure which will reach the best audience.) As you may be aware, PECL contains two extensions for connecting to memcache: one called "memcache", and one called "memcached". This has always been a great source of confusion, particularly because their introductions in the manual [1][2], don't even acknowledge the existence of the other, let alone explain why you'd choose one or the other. However, it seems that the package without a d is actually abandoned. The official PECL package was last released more than 5 years ago [3], and the bug asking for PHP 7 compatibility is still open [4]. An unofficial fork apparently supports PHP 7 [5] but it in turn hasn't had a commit in 11 months, and has an open bug for 7.2 compatibility [6]. The package with a d, on the other hand, appears at a glance to be actively maintained, and would seem to be the right choice for any user writing new code. How can we make this more useful? - Is there any difference, other than API design, between the two packages, which would merit seeking a new maintainer for memcache (without a d)? - If not, should the package be officially marked "abandoned" or "deprecated" in PECL, and in the PHP manual? - Either way, should the manual for memcache (without a d) direct users to use memcached (with a d) for all new code? If not, what advice should it give? Thank you for any pointers or opinions! References: [1]: http://php.net/manual/en/intro.memcache.php [2]: http://php.net/manual/en/intro.memcached.php [3]: https://pecl.php.net/package/memcache [4]: https://bugs.php.net/bug.php?id=72887 [5]: https://github.com/websupport-sk/pecl-memcache [6]: https://github.com/websupport-sk/pecl-memcache/issues/28 [For those who don't get the joke in the subject line: https://en.wikipedia.org/wiki/Thomson_and_Thompson] Regards, -- Rowan Collins [IMSoP]