Pierangelo Masarati wrote:
The patch I just committed does exactly that: as soon as an entry, within a query response, would not match the filter when applied locally, the entire query is not catched. This causes a little performance degradation because the filter also needs to be applied by the proxy. The query will always be answered resorting to the remote server, unless the proxy administrator fixes the schema.
The final version of the patch makes the additional check optional, conditioned on the presence of the "proxycheckcacheability TRUE" directive (olcProxyCheckCacheability attribute in back-config). This allows proxies with well-configured schema to avoid the overhead related to double-filtering.
p. PS: Quanah, sorry for the extra work ;) 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 Fax: +39 0382 476497 Email: [EMAIL PROTECTED] ----------------------------------- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
