> but we should also allow for the client to push the
> analysis
> responsibility to the server:
Yet another variation we could support is to use the
existing QueryParser server-side for handling
user-typed input. On the client user input is unparsed
and combined with the lower-level constraints created
by application code e.g:
<BoostingQuery>
<MatchQuery>
<!-- user typed-input passed through here -->
<UserQueryParser defaultField="contents"
analyzer="xxxx">
"some phrase"
</UserQueryParser>
</MatchQuery>
<BoosterQuery boost="1.5">
<!-- criteria supplied by app code here
e.g. user profile built by observing
behaviour-->
<BooleanQuery>
<q occ="should"><Term
field="keywords">Java</Term>
<q occ="should"><Term
field="keywords">XML</Term>
</BooleanQuery>
</BoosterQuery>
</BoostingQuery>
<!-- ....plus any other app-code created criteria eg
date/price range filters -->
___________________________________________________________
How much free photo storage do you get? Store your holiday
snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
