Menu
▾
▴
On Tue, Aug 01, 2000 at 03:02:56PM -0500, Mark Wilcox wrote: > The server likely won't return any more than 1000 entries (though this is > a server configuration) unless you're binded to the server as the > directory super-user or using a server control like Paged Control, or the > more popular Virtual List View. > > You can also limit the results by setting a more direct base > (e.g. ou=people,o=unt.edu instead of just o=unt.edu), scope and/or a > filter that's more specific. > > BTW Graham, most of the other LDAP APIs have a parameter in search to > limit the number of results. So does Net::LDAP, the sizelimit option. I just forgot about it :)
Content-Type: multipart/alternative; boundary="------------030807020302050603060500" --------------030807020302050603060500 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit If I'm using Paged Search and having to re-send the search request to the server with the cookie to get the next page, does this mean that as long as the sizelimit is greater than the page size, there will always be a "next page" until the entire contents of the directory have been consumed? Even if there are server side limits? --Darryl ------------------------------------------------------------------------ On Tue, Aug 01, 2000 at 03:02:56PM -0500, Mark Wilcox wrote: > The server likely won't return any more than 1000 entries (though this is > a server configuration) unless you're binded to the server as the *> directory super-user or using a server control like Paged Control, or the *> more popular Virtual List View. > > You can also limit the results by setting a more direct base > (e.g. ou=people,o=unt.edu instead of just o=unt.edu), scope and/or a > filter that's more specific. > > BTW Graham, most of the other LDAP APIs have a parameter in search to > limit the number of results. >So does Net::LDAP, the sizelimit option. I just forgot about it :) >It's also not documented that well, which I have hopefully fixed for .20 Graham. ------------------------------------------------------------------------ --------------030807020302050603060500 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit <html><head></head><body>If I'm using Paged Search and having to re-send the search request to the server with the<br> cookie to get the next page, does this mean that as long as the sizelimit is greater than the page size, there will always be a "next page" until the entire contents of the directory have been consumed? Even if there are server side limits?<br> <br> <br> --Darryl<br> <hr><!--X-Head-Body-Sep-End--><!--X-Body-of-Message--><pre>On Tue, Aug 01, 2000 at 03:02:56PM -0500, Mark Wilcox wrote:<br>> The server likely won't return any more than 1000 entries (though this is<br>> a server configuration) unless you're binded to the server as the<br><a name="mfs"><b>> directory super-user or using a server control like Paged Control, or the<br> </b></a>> more popular Virtual List View.<br>> <br>> You can also limit the results by setting a more direct base<br>> (e.g. ou=people,o=unt.edu instead of just o=unt.edu), scope and/or a<br>> filter that's more specific.<br>> <br>> BTW Graham, most of the other LDAP APIs have a parameter in search to<br>> limit the number of results.<br><br>>So does Net::LDAP, the sizelimit option. I just forgot about it :)<br><br>>It's also not documented that well, which I have hopefully fixed for .20<br><br>Graham.<br><br></pre> <!--X-MsgBody-End--><!--X-Follow-Ups--><!--X-Follow-Ups-End--><!--X-References--> <hr></body></html> --------------030807020302050603060500-- |
