Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:26852
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 66.249.92.173 as permitted sender)
DomainKey-Status: good
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=NjaFSKIWXlxUE0d/ZaOzti0mqbc4oQ80wVZcW6zyCwzqp52AHIH1P2sNn5UAIW8gZ+onjaDExAG6xcdZX62kGfabl3kQ+PXTvxBjIwb7lQw20rH2caCl0z9oYA6dBJhBAuglV+4SssWtzOJmVF6YSa3Zc2BSWrnB+fDtmw0/jT0=
Message-ID: <fe05d1540612081124n250263f4ka85d372c7c0c895e@mail.gmail.com>
Date: Fri, 8 Dec 2006 20:24:58 +0100
To: "Ilia Alshanetsky" <ilia@prohost.org>
Cc: "PHP internals" <internals@lists.php.net>
In-Reply-To: <3B40503A-75F6-41EC-BFCF-56D777501FA5@prohost.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <3B40503A-75F6-41EC-BFCF-56D777501FA5@prohost.org>
Subject: Re: [PHP-DEV] Moving COM, Socket & mhash to PECL
From: pierre.php@gmail.com (Pierre)

Hello,

On 12/8/06, Ilia Alshanetsky <ilia@prohost.org> wrote:
> This is an exploratory e-mail,  so don't panic just yet :-). I am
> thinking of moving the COM, mhash and socket extensions to PECL in
> 5.2 and 6.0 releases and was hoping to hear for & against arguments.
> The reason for the making this move are as follows:
>
> COM:
>         Un-maintained at this time and has a fairly serious number of bugs
> (26 by latest count, many of which are crashes)

It has a lot of bugs yes, but it is useful and works well for many
situations. I do not like the idea to move it out of php.

>         Moving it to PECL will allow for an independent release cycle, which
> may allow for faster fix deployment etc...

It is possible without moving it out. It could even be a good thing to do it.

>         I hoping the move will encourage people and/or companies to start
> maintaining the extension.

There is bugs and it is expected, COM allows a lot of things with a
lot of external apps, no wonder. But it works well (for what I did at
least, office, IE and XML com). I can try to take a look at the open
bugs if Wez is missing the time.

> mhash:
>         Everything this extension that relies on an external lib to do, is
> already done by hash extension that is enabled by default and
> requires no external libs. There is simply no reason to keep it around.

We may move it from php 6.0 and up or at least from 5.3.0.

> sockets:
>         Un-maintained.
>         Majority of what it can do can already by done via streams in a much
> more consistent and stable fashion.

+1 from php 6.0 and up but I'm worrying a bit about 5.x code relying on it.

--Pierre