No. That'd be quite silly, wouldn't it ?
Absolutely :), that's why I was curious.
So correct me if this wrong, but sounds like either of the two can be
used to limit how much the server works on a search, but they each take
effect at a different part of the search algorithm.
I still wonder why you'd choose one over the other to implement result
limits? Seems kind of like a door with two knobs. Maybe there's some
specific cases where one is preferable.
Thanks again for the replies,
-- George
David Boreham wrote:
George Holbert wrote:
The notion behind lookthrough limit is that the administrator
can dermine an upper bound for the amount of WORK that
the server will perform for a given client's search.
That makes sense.
Does this mean if a sizelimit (not lookthrough) is hit, the server
continues searching the database, even though it has already returned
error code 4 to the client?
No. That'd be quite silly, wouldn't it ?
It _might_ do a bunch of work up front to service a search
only to discover when sending entries back to the client that the
size limit is exceeded.
--
Fedora-directory-users mailing list
Fedora-directory-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-directory-users
