Doug Cutting wrote:
Chuck Williams wrote:
I think the question is how frequent and how expensive would those two
steps be in comparison to the difference in the query processing.
I think the first question is: can we get RemoteSearchables to work
correctly and reasonably efficiently for simple queries?
I'd like to add another point: when it comes to caching, I'm convinced
that one size does *not* fit all. We won't be able to find *the*
optimal approach to distributed scoring. Therefore IMHO we should
strive for a solution that:
- works reasonably fast for reasonably simple queries out of the box.
- is flexible and configurable so that people can optimize according
to their context by replacing the default strategy with their own
one.
To make sure the latter is the case, it might be a good idea to
check if Chuck's proposal would be implementable as custom strategy
based on the Interfaces we're going to de-/re-fine. But IMHO it is much
too complex for a default strategy.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
