Re: [discuss] [Really last] Why are quoted searches sohard toimplement?

From: "Sam Berlin" <[email protected]>
>I think the ultimate solution will have the server-side start parsing 
>queries that contain quotes, as well as the GGEP extension of quotes.  For 
>a while we'll send out queries with the quotes stripped out & placed into 
>the GGEP portion, so that _some_ results are still sent from older clients. 
>Once a good amount has upgraded, we can shut off including quotes in GGEP 
>and just place them into the search itself (this can be remotely signaled). 
>We also can't use any delimiters that are also in SearchSettings.BAD_CHARS, 
>because all LimeWires will drop those queries.

Why couldn't it be enough to insert quotes in the normal search string?

Legacy servers will ignore those quotes anyway (in the routines that parse 
and simplify the search string and split it into indexable keywords for QRP, 
or matching keywords for the local library), and will return results 
matching enough keywords in any order, but new servers will not ignore them.

Isn't what Bearshare already does?

Also, should quoted searches match words exactly, or with unsignificant 
case? If exact match is required, this will probably require adding some 
search-semantics bits in GGEP. I see little interest in augmenting too much 
the Query message length by duplicating the string...


_______________________________________________
discuss mailing list
[email protected]
http://www.limewire.org/mailman/listinfo/discuss