On 7/18/06, Chris Hostetter <[EMAIL PROTECTED]> wrote:
: Field properties could be made more than a convention... the : f.field.property=val stuff could be parsed out to easier-to-use : objects by PluginUtils. But they are optional, and I don't see : f.foo.fragsize=0 being more complicated than having to write your own : custom query handler ;-) certainly ... i'm just not clear if there are a lot of cases where that much flexability is really needed at query time -- as opposed to in the solrconfig where it can more easily be expressed.
Multiple sites could query a common search collection, or probably more likely, different pages on the same site may want different fragment sizes. As a common example, look at google groups... there are small fragments in the summary page, and then large fragments (or the complete message) highlighted when you go to the thread view. I could even see a site wanting the user to be able to customize the sizes. I guess it is primarily an issue of aesthetics... we do want to avoid making things ugly (query args, configuration, etc) while we make things as powerful and flexible as possible. -Yonik
