Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:18522 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 31512 invoked by uid 1010); 29 Aug 2005 12:08:42 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 31497 invoked from network); 29 Aug 2005 12:08:42 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 29 Aug 2005 12:08:42 -0000 X-Host-Fingerprint: 212.18.24.66 host-212-18-24-66.customer.m-online.net Received: from ([212.18.24.66:26153] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 70/BB-15098-ACAF2134 for ; Mon, 29 Aug 2005 08:08:42 -0400 To: internals@lists.php.net Date: Mon, 29 Aug 2005 14:08:02 +0200 Message-ID: <20050829140802.4011ee5f.pierre@dotgeek.org> References: <43110D8D.9080008@lerdorf.com> <1125193332.27570.4.camel@localhost.localdomain> <12fe01c5abdc$229e6d50$9cd96751@foxbox> <1125269439.27570.16.camel@localhost.localdomain> <16a201c5ac8c$271c4450$9cd96751@foxbox> <1125316713.11271.5.camel@localhost.localdomain> X-Newsreader: Sylpheed version 2.0.0beta6 (GTK+ 2.6.9; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Posted-By: 212.18.24.66 Subject: Re: [PHP-DEV] Re: PHP 5.1: Does it still require ext/xmlrpc for pear? From: pierre@dotgeek.org (Pierre-Alain Joye) On Mon, 29 Aug 2005 07:58:33 -0400 john@coggeshall.org (John Coggeshall) wrote: > On Mon, 2005-08-29 at 13:23 +0200, Steph wrote: > > It's the 'given that it doesn't appear to have an active > > maintainer' part that's important here. It takes a little TLC > > to make a PECL package available for download. > > I'll roll the PECL package myself. Hang on, I'm really not sure it's either good or worth the effort to do that. Some reasons: - ext/xml_rpc was kept there mainly for pear, sadly was not enabled by default which makes it pretty useless for shared hosts and friends - xmlrpci do not bring anything but overloading (for the client part, server being not in cvs last time I checked) - Webservices (xmlrpc, soap,...) should rely on smaller memory usages and faster processing that the default libxml2 parsers (dom and related functions), ie xmlreader and xmlwriter, in libxml not the php extension In my opinion, xmlrpci _and_ xmlrpc perfectly fit in pecl from php 6 and up. Adding one is only adding more confusions. Regards, --Pierre