Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:31348
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.198.186 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=ckjsDGspQaRWRXoVNnyr88N1YOMEcVhrujM/jOdEpEK8qwOyyDa8DlPRb/qsUk92qW0I4s+Np2rG/s4Il2Jbnkg/P6l3UKFC5Yryy/kn4CJpOCFAONk/I9Jcc74xBaUStTn368Tywz2daPFWL6PlCwDaQ2KP7lbQf2T0NPpJjgg=
Message-ID: <fe05d1540708010123q72557ae2h5529b751cfc1dd5f@mail.gmail.com>
Date: Wed, 1 Aug 2007 10:23:12 +0200
To: "Daniel Stenberg" <daniel@haxx.se>
Cc: internals@lists.php.net
In-Reply-To: <Pine.LNX.4.64.0707312229390.9543@yvahk3.pbagnpgbe.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <Pine.LNX.4.64.0707301316440.22586@yvahk3.pbagnpgbe.fr>
	 <46AF6536.4010600@lerdorf.com>
	 <Pine.LNX.4.64.0707312229390.9543@yvahk3.pbagnpgbe.fr>
Subject: Re: [PHP-DEV] Regarding the ext/curl extension
From: pierre.php@gmail.com (Pierre)

Hi Daniel,

On 7/31/07, Daniel Stenberg <daniel@haxx.se> 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).
>
> Now they search for curl and libcurl instead, and they read the docs on our
> site, and yes some of them get angry or even hostile on us when they can't
> find enough details about PHP on our curl site.

I would like to suggest you a few things I did for libgd. It has the
same problem (even worst, as PHP forked gd a few years back).

- Add abinding entry in the navigation menu in all your pages (not
only for libcurl)

- Add a notice (in bold, italic and red :) on the homepages (curl and
libcurl)  that you have nothing to do with the binding and put a link
to the binding page (which should only have a "see
myfavouritescriptinglanguage.net/curl" for further details)

- Drop the PHP doc on your site as soon as you consider the PHP manual
as good enough

But pushing the PHP docs (as Steph suggested later) to your site will
only bring you more questions about php's CURL binding. It sounds like
a bad idea :)

Cheers
--Pierre