Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:31346
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain zend.com from 64.97.136.175 cause and error)
Message-ID: <07e601c7d3cf$c4567580$49fc1f3e@foxbox>
Reply-To: "Steph Fox" <steph@zend.com>
To: "Derick Rethans" <derick@php.net>,
	"Daniel Stenberg" <daniel@haxx.se>
Cc: <internals@lists.php.net>
References: <Pine.LNX.4.64.0707301316440.22586@yvahk3.pbagnpgbe.fr> <46AF6536.4010600@lerdorf.com> <Pine.LNX.4.64.0707312229390.9543@yvahk3.pbagnpgbe.fr> <alpine.DEB.0.98.0707312246260.19202@kossu.ez.no>
Date: Wed, 1 Aug 2007 01:06:09 +0100
Organization: Zend Technologies
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="UTF-8";
	reply-type=original
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Regarding the ext/curl extension
From: steph@zend.com ("Steph Fox")

Guys,

I don't think battling helps anyone.

I thought Daniel and myself had come to an (admittedly vague) agreement last 
week that a good way to approach this might be by fixing the php.net docs to 
give all the PHP-related info currently held on the libcurl site, and then 
ditch that page on the libcurl site and just link to the downloads rather 
than the libcurl project homepage.

As you might gather from that, I do agree with Daniel that the current setup 
with ext/curl is utterly confusing for PHP users. I don't really care whose 
fault it is, it just needs fixing.

Gwynne and myself have been talking under cover, and it seems we both are 
keen to do something with this. She has other projects outstanding at 
present (mainly the phpdoc build system) and I have a bunch of commitments 
to fulfill before I head off on holiday. For both of us, September's the 
first sane attack date when it comes to ext/curl.

There's also a bit more to this than straightforward documentation. I think 
I mentioned already.

Can we please drop this now until we both have space to work on it? After 
all, the status quo didn't arrive overnight.

Cheers,

- Steph

----- Original Message ----- 
From: "Derick Rethans" <derick@php.net>
To: "Daniel Stenberg" <daniel@haxx.se>
Cc: <internals@lists.php.net>
Sent: Tuesday, July 31, 2007 9:48 PM
Subject: Re: [PHP-DEV] Regarding the ext/curl extension


> On Tue, 31 Jul 2007, Daniel Stenberg wrote:
>
>> On Tue, 31 Jul 2007, Rasmus Lerdorf wrote:
>>
>> > Daniel, I don't really understand what renaming the extension would
>> > accomplish.
>>
>> Then I didn't make myself clear.
>>
>> The point of renaming would be to allow people to search for something
>> with a name that doesn't confuse them. If the binding would be called
>> 'mombamoolo', they would search for that and they would certainly not
>> be confused by products or projects called curl or libcurl (even if
>> they would know that mombamoolo uses libcurl).
>
> This has another side as well. If it was called mombamoolo then how
> would people know that PHP is actually providing a wrapper for curl?
> There have been some examples of this in the past "sattelite" and
> "universe" where both extensions around corba for example- and if you
> didn't know you'd have no idea where to look for. So I'd say that with
> picking a different name you'd confuse people.
>
> regards,
> Derick
>
> -- 
> Derick Rethans
> http://derickrethans.nl | http://ez.no | http://xdebug.org
>
> -- 
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>