Hello, I'm trying to write a MultiSearcher/ParallelMultiSearcher variation that uses JMS to talk to its subordinate Searchers. While running through MultiSearcher to see where I can save some cycles or network hops, I came across Query.combine(). It's called from MultiSearcher.rewrite() (as you know) but seems to be there only to allow for different Searcher implementations in MultiSearcher's subordinate Searchers. So, am I correct in assuming that, if I use the same Searcher to query every subordinate index, I can save myself a network hop by rewriting/combine()ing the Query once, in the JMS MultiSearcher?
Every other time I thought I'd found an optimization it turned out to be written the way it was for a reason. I'm wondering if that's going to be the case here, too -- hence the question. Thanks for the help. -joe __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
