: I suspect that 3 is actually better. You can use CachingWrapperFilter to
I'm not so sure of that ... if you've got thousands of mailing lists, some
of which are used very infrequently, and you don't *ever* need to search
more then one at a time then having a seperate index for each will help
red
I suspect that 3 is actually better. You can use CachingWrapperFilter to
cache the filters automatically. Also, I found that filters were much faster
to construct than I first thought.
That said, though, why bother with a filter? Why not just make the list part
of the query and let Lucene take ca
Hi. I'm the lead developer of SubEtha, a new java open source mailing
list manager (http://subetha.tigris.org/). I'm working on archive
searching at the moment. I've used Lucene with great success in a
previous application, but some of the characteristics of this app have
me seeking architec
