Re: Re: memcache, without a d, as in Venezuela
| From: | Christoph M. Becker | Date: | Thu, 19 Dec 2019 12:51:50 +0000 |
| Subject: | Re: Re: memcache, without a d, as in Venezuela | ||
| References: | 1 2 3 4 5 | Groups: | php.internals php.pecl.dev |
| Request: | Send a blank email to internals+get-107928@lists.php.net to get a copy of this message | ||
On 20.11.2018 at 11:26, Rowan Collins wrote:
> On Mon, 19 Nov 2018 at 15:53, Pierre Joye <pierre.php@gmail.com> wrote:
>
>> On Sun, Jun 24, 2018, 12:00 AM AllenJB <php.lists@allenjb.me.uk wrote:
>>
>>> Someone was asking about memcache vs memached on IRC the other day and I
>>> advised them the memcache extension looked abandoned based on the PECL
>>> page. Having 2 such similar extensions is confusing - It would also be
>>> nice if someone could document the major differences between the 2
>>> extensions somewhere to help users decide which they might want to
>>> select.
>>
>> memcached uses libmemcache, which only supports linux-like systems. This is
>> the main reason to keep both.
>
> That doesn't entirely follow: it's a reason why not to abandon the
> without-a-d extension, but it doesn't actually justify keeping both.
>
> It seems to me that *neither* extension is properly maintained right now
> (the with-a-d extension has recent releases, but all wrapping an abandoned
> upstream library); so if the without-a-d extension has better
> cross-platform support, it might make sense to keep *only* that one
> (revived from https://github.com/websupport-sk/pecl-memcache)
> and encourage
> anyone interested to contribute rather than splitting the effort.
FWIW, PECL/memcache has had a new release today. \o/
--
Christoph M. Becker