[Date Prev][Date Next]
RE: RE: Overlay Documentation
That's a good idea. Would be good also to let the admin of the proxy cache
decide about that in the config file.
Am i wrong about that ?
From: Apurva Kumar [mailto:firstname.lastname@example.org]
Sent: venerdì 19 marzo 2004 11.56
To: Voglmaier, Reinhard Erich
Subject: RE: RE: Overlay Documentation
If a search request is abandoned, back-ldap proxies the abandon request to
the backend server. In this case nothing goes into the cache. Salvaging such
requests to obtain the complete result set will be some kind of prefetching.
A more useful form of prefetching could be fetching more general filters
Research Staff Member,
IBM India Research Lab
Reinhard Erich" To: Apurva
Subject: RE: RE: Overlay
03/19/04 03:01 PM
This one is interesting:
"A query Q is cacheable if there is a proxyTemplate with an identical
prototype filter and the same set of requested attributes as Q and it
fetches <= K entries where K is the entry limit specified in the proxyCache
My question now: What happens with aborted queries ? Let's assume the
queryset reports K entries ( K < sizelimit ) and the client interrupts the
transfer after , lets say , 10% of K. What goes into the cache ? Does the
proxy request the remaining 90% and put it in it's cache anyway ? Could this
be configured by the administrator ? It would be good to be configurable,
because in some environment it could be a performance gain to store also
aborted query results, in some it could be a performance loss.