> Date: Mon, 10 Jan 2005 10:01:33 -0000
> From: "Matthew J. Dovey" <[log in to unmask]>
>
> The current definition says "'cql.serverChoice' means that the
> server will choose an index for the given term ... By contrast,
> cql.serverChoice means essentially "search any index -- your choice
> -- from any context set you know" i.e. that the client doesn't care
> what server known context set index is used (nothing more)

Yes -- cql.serverChoice means any index that the server _knows_.  It
says nothing about it having to be an index that the server _exposes_.

In conclusion, I argue that all six of Matthew's suggested
interpretations are valid for cql.serverChoice, and I concur with the
general sentiment that the current prose should be tightened up.  I
also think there may be a role for more specific "any"-like indexes
corresponding to specific interpretations on Matthew's list (and maybe
other interpretations not on that list, including the interpretation
"search all fields even if they're not indexed, using grep on the raw
data files if necessary").

 _/|_    _______________________________________________________________
/o ) \/  Mike Taylor  <[log in to unmask]>  http://www.miketaylor.org.uk
)_v__/\  "Sixteen is a compromise between not very many and quite a
         lot" -- Mike Selway.

--
Listen to free demos of soundtrack music for film, TV and radio
        http://www.pipedreaming.org.uk/soundtrack/