On 27.01.23 17:28, Christoph M. Becker wrote:
On 27.01.2023 at 17:06, Levi Morrison via internals wrote:
On Fri, Jan 27, 2023 at 8:54 AM Larry Garfield wrote:
On Fri, Jan 27, 2023, at 3:00 AM, Andreas Heigl wrote:
I think it would be a good idea to deprecate calling ldap_connect with 2
par
On Fri, Jan 27, 2023, at 10:28 AM, Christoph M. Becker wrote:
> On 27.01.2023 at 17:06, Levi Morrison via internals wrote:
>
>> On Fri, Jan 27, 2023 at 8:54 AM Larry Garfield
>> wrote:
>>>
>>> On Fri, Jan 27, 2023, at 3:00 AM, Andreas Heigl wrote:
>>>
I think it would be a good idea to depre
On 27.01.2023 at 17:06, Levi Morrison via internals wrote:
> On Fri, Jan 27, 2023 at 8:54 AM Larry Garfield wrote:
>>
>> On Fri, Jan 27, 2023, at 3:00 AM, Andreas Heigl wrote:
>>
>>> I think it would be a good idea to deprecate calling ldap_connect with 2
>>> parameters host and port.
>>
>> This
On Fri, Jan 27, 2023 at 8:54 AM Larry Garfield wrote:
>
> On Fri, Jan 27, 2023, at 3:00 AM, Andreas Heigl wrote:
> > Hey Folks.
> >
> > I think it would be a good idea to deprecate calling ldap_connect with 2
> > parameters host and port.
> >
> > Wait: What?
> >
> > Currently there are three ways
On Fri, Jan 27, 2023, at 3:00 AM, Andreas Heigl wrote:
> Hey Folks.
>
> I think it would be a good idea to deprecate calling ldap_connect with 2
> parameters host and port.
>
> Wait: What?
>
> Currently there are three ways one can call ldap_connect.
>
> 1. With a string $ldap_uri
> 2. With a stri
Hey Folks.
I think it would be a good idea to deprecate calling ldap_connect with 2
parameters host and port.
Wait: What?
Currently there are three ways one can call ldap_connect.
1. With a string $ldap_uri
2. With a string $host and an int $port,
3. With even more parameters for those that
