Howard Chu wrote:
> Right. Well, I understand if no limit was hit the request would
become
> cacheable. In this case, the approach you suggest would be fine.
Of course the result size has to also fit within the cache's configured
size limit. We may want to add another type of negative caching record
here for this case "we already know the result set is too large, ignore
the cache DB"...
I'm getting inclined towards handling this case like a regular search,
only replacing LDAP_SUCCESS with LDAP_SIZELIMIT_EXCEEDED. In fact, it
would be more appropriate to make this request not cacheable, because
there's no guarantee the server would return the same entries for
repeated searches, but for caching purposes this shouldn't really matter.
p.
Ing. Pierangelo Masarati
OpenLDAP Core Team
SysNet s.r.l.
via Dossi, 8 - 27100 Pavia - ITALIA
http://www.sys-net.it
---------------------------------------
Office: +39 02 23998309
Mobile: +39 333 4963172
Email: pierangelo.masarati(a)sys-net.it
---------------------------------------