Russell Wilton wrote:
> David J Kernen wrote:
>
> > I doubt that ldapsearch (and similarly but in an opposite direction,
> > ldapmodify) do anything special to maintain order; they just process
> > what they're given in the order they receive it because that's the
> > easiest way.
>
> That's all I wanted Perldap to do too. Just process them in the order it
> receives them. I'm pretty sure that Perldap does do that on reading, just
> not on writing. Unfortunately, Perl hashes don't maintain any order, so for
> Perldap, it's NOT the easiest way. I guess nobody but me thinks it's worth
> the trouble to work around that.
I'm gonna go through all old perldap bugs, and new bugs, and use this for a
v2.0 PerLDAP "plan"... I'll add the request above as an RFE for v2.0, it's the
best we can do for now (I don't have the time for doing more work on
PerLDAP v1.4).
Also, if there are people out there who'd like to contribute to PerLDAP, please
step up. I'm really sorry that development of PerLDAP has grinded to a halt,
but sometimes real life just sucks you in... I still think we can make a
PerLDAP v2.0 that kicks ass, I have some major changes going in, like switching
to async I/O, totally change argument passing etc.. This will allow us to use
new LDAP v3 features as well, like controls.
Cheers!
-- leif
