Well, there's a part of the application that you're not seeing that does the checking of the index state. This is done inside of what is essentially a wrapper to a map which clears all filters upon a state change in the index. Your point is perfectly valid however for anyone who does not have such a wrapper and one that I should have mentioned in my previous email.
So, if there was a caching filter implemented like yours, but with the WeakHashMap cache like QueryFilter, would you use it instead of what you've done? I'm in agreement with you about where the caching should be. Would anyone object to such an implementation added to Lucene's core?
Erik
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
