ability to deal with paginated results for LDAP servers

[ssbarnea]

Most LDAP servers do have server side limits regarding the number of entries they do return to the clients, and this limits cannot be changed by the client (it's not the client specified limit).

A couple of years a ago I wrote a similar library that was on top of python-ldap, that was hiding all the complexity of working with paginated results and I would like to make it public.

Imagine that in my case I do have to work with an a tree of LDAP/AD servers that do return ~14.000 users and ~20.000 groups, and the server side limit is 1000. It would be impossible to work without pagination.

Now, my question is if I should add yet-another-ldap-pypi package or I should add my features to an existing one, like this one. Ideally I would like to bring my changes to python-ldap itself but I guess that's much harder.

What do you think about this?

[gdub]

Sounds like it would be a nice addition, and exactly the kind of annoyance that this library tries to make more simple.

[rosshamish]

Is there still interest in pagination support for searches? I'd be willing to pull the feature in.

[gdub]

@rosshamish If you have interest in the feature, then by all means have a go at it and submit a pull request.

[ssbarnea]

Sorry but meanwhile we decided to go for https://pypi.python.org/pypi/python3-ldap which has pagination support and is pure python (no need to compile) and I implemented https://pypi.python.org/pypi/activedirectory on top of it for performing tasks very easly with AD. I doubt I will ever look back on other python LDAP libraries.

BTW, from what I heard, the python3-ldap library aims on replacing the current Python own ldap implementation. Do no be confused about its naming, is does work with Python 2.x too, this is how I use it.

[rosshamish]

@ssbarnea Thanks for the tip on python3-ldap, I'm now considering migrating to it from python-ldap. From the name, I assumed it would be incompatible with Python 2.x, which my current project is bound to because of library support. I was wrong!

@gdub If python3-ldap doesn't work out for me, I'll likely submit a pull request. Otherwise, I'll just use python3-ldap. Thanks for the reply.