You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of this looks like a real nice project! There is certainly room for an abstraction over ldap3 (which I'm using currently).
Is your feature request related to a problem? Please describe.
I want to execute a steaming search and "process" the individual results asynchronously. I'm expecting the search results to be big, so I don't want to store it in memory all at once.
Describe the solution you'd like
streaming_search should return a stream instead of a vector containing all the results.
In practice it would be a wrapper object around ldap3::SearchStream that implements the stream trait. SearchStream already takes care of the pagination, so probably this could be done with very little logic here.
Describe alternatives you've considered
The same thing could be done upstream in the ldap3 crate, but probably they just want to mirror the LDAP protocol more closely in their API.
Additional context
It would still be relatively simple to just collect the stream into a Vec if the user just wants all the results at once.
The text was updated successfully, but these errors were encountered:
First of this looks like a real nice project! There is certainly room for an abstraction over
ldap3
(which I'm using currently).Is your feature request related to a problem? Please describe.
I want to execute a steaming search and "process" the individual results asynchronously. I'm expecting the search results to be big, so I don't want to store it in memory all at once.
Describe the solution you'd like
streaming_search
should return astream
instead of a vector containing all the results.In practice it would be a wrapper object around
ldap3::SearchStream
that implements thestream
trait.SearchStream
already takes care of the pagination, so probably this could be done with very little logic here.Describe alternatives you've considered
The same thing could be done upstream in the
ldap3
crate, but probably they just want to mirror the LDAP protocol more closely in their API.Additional context
It would still be relatively simple to just
collect
the stream into aVec
if the user just wants all the results at once.The text was updated successfully, but these errors were encountered: