: Hmmm, no reason I see. : Unless there are objections, I'll make them public.
-0 ... i'd much rather see us deprecate it and make it go away entirely. it's an archaic throwback to the days when every option was going to be encoded into the "q" param instead of having "sort" "rows" and "start" (ie: q = solr rocks; price asc, score desc, skip 50, top 10 ... or something like that) Last time i looked at most usages, the getOffset() and getCount() were totally ignored and the only reason any class refered to SortSpec was because they had to (since there is no parseSort that just returned a Sort object) A quick grep indicates that the new QParser and QueryComponent stuff (which i still haven't had time to look at) seems to be using it, but i can't tell if that's just because that's what's parseSort returns, or if it's becuse it's actually useful to have those three values bundled in that way. if we're going to keep it, let's at least put some mutators on it ... and maybe consider changing the name. -Hoss
