Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:86874
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: fail (pb1.pair.com: domain opensides.be does not designate 62.210.211.30 as permitted sender)
Message-ID: <558C2DAD.1010905@opensides.be>
Date: Thu, 25 Jun 2015 18:34:53 +0200
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Anatol Belski <anatol.php@belski.net>, 
 'Andreas Heigl' <andreas@heigl.org>,
 internals@lists.php.net
CC: 'Kalle Sommer Nielsen' <kalle@php.net>, 
 'Ferenc Kovacs' <tyra3l@gmail.com>
References: <558ACF4D.6030506@heigl.org> <07fd01d0af5f$8f648d70$ae2da850$@belski.net>
In-Reply-To: <07fd01d0af5f$8f648d70$ae2da850$@belski.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] Deprecating ldap_sort
From: come.bernigaud@opensides.be (=?UTF-8?B?Q8O0bWUgQkVSTklHQVVE?=)

Le 25/06/2015 17:56, Anatol Belski a écrit :
> I've a few questions to this. Can it be implemented with non deprecated symbols? Or maybe, can the server side sort not be done with the same function, as it's probably the same job? Or it will be really not required? Any info about the plans on the openldap side to remove the deprecated symbols (AFAIR those are kept already for years)?
No, it can’t be implemented without deprecated symbol, neither with 
server side sort.
Here is the workflow:
call to ldap_search
call to ldap_sort
call to get the results (for instance ldap_get_entries)

Server sort would have to be set before the search itself. Other tools 
like php array sorting features will take place after the results.
So, this function have no easy drop in replacement, we’ve looked into 
that. I also asked on openldap mailing list.
But it is useless as it can be replaced by either server side sort or 
classic PHP array sorting functions.
> We're currently don't know, how wide this function is used and how much it would break. In general, deprecating it if there's a strong reason, could be sufficient. If there's a small possibility to keep this function, we should use it. Fe maybe it could kept and enabled with a configure option, that way it'll be still usable.
It’s mainly a proxy to an openldap function which is deprecated since at 
least 2007. And the function is useless and easily replacable by other 
PHP functions.
> Any feedback from the ldap users were appreciated here, as well.
>
> Regards
>
> Anatol
Côme