Hi Daniel, On 7/31/07, Daniel Stenberg <[EMAIL PROTECTED]> 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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
