Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:26851
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.25.124.162 as permitted sender)
To: "'Ilia Alshanetsky'" <ilia@prohost.org>,
	"'PHP internals'" <internals@lists.php.net>
Date: Fri, 8 Dec 2006 10:30:50 -0800
Message-ID: <009101c71af6$fe795530$6600a8c0@zend.2k>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acca4nYekhwZ0PmuTVKZlxkyvymXkAAE+y0g
In-Reply-To: <3B40503A-75F6-41EC-BFCF-56D777501FA5@prohost.org>
Subject: RE: [PHP-DEV] Moving COM, Socket & mhash to PECL
From: andi@zend.com ("Andi Gutmans")
References: <3B40503A-75F6-41EC-BFCF-56D777501FA5@prohost.org>

I'm OK with all except for COM.
I've actually used the COM extension quite a bit internally here for
reporting and creating Excel files (see one of my blog postings from about a
year ago). I think for those who are on Windows it's a really handy
extension. Last time I checked it was also always enabled and available
which is useful. It also makes sense because when other modules need COM to
be initialized it shoud be done only once in the PHP core and so should be
available (kind of like libxml serves the other XML extensions).

As far as finding a maintainer is concerned, we can check again with Wez. If
he doesn't have time we should probably be able to find someone who can look
into some of those bugs. Despite bugs, I've never had issues with it.

Andi


> -----Original Message-----
> From: Ilia Alshanetsky [mailto:iliaal@gmail.com] On Behalf Of 
> Ilia Alshanetsky
> Sent: Friday, December 08, 2006 8:03 AM
> To: PHP internals
> Subject: [PHP-DEV] Moving COM, Socket & mhash to PECL
> 
> 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)
> 	Only usable to Win32 users, which I think we all admit 
> are a minority and can always download readily available 
> binaries from pec4win. Since most of them don't compile the 
> extension from source anyway there is IMHO little reason to 
> bundle the sources with every php package.
> 	Moving it to PECL will allow for an independent release 
> cycle, which may allow for faster fix deployment etc...
> 	I hoping the move will encourage people and/or 
> companies to start maintaining the extension.
> 
> 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.
> 
> sockets:
> 	Un-maintained.
> 	Majority of what it can do can already by done via 
> streams in a much more consistent and stable fashion.
> 
> 
> Ilia Alshanetsky
> 
> --
> PHP Internals - PHP Runtime Development Mailing List To 
> unsubscribe, visit: http://www.php.net/unsub.php
>