W3C home > Mailing lists > Public > www-zig@w3.org > September 2001

Re: Sort criteria in Search Request

From: Mike Taylor <mike@tecc.co.uk>
Date: Mon, 17 Sep 2001 12:21:04 +0100
To: ian.ibbotson@k-int.com
CC: www-zig@w3.org
Message-Id: <E15iwSW-0002ow-00@fw-smtp.tecc.co.uk>
> Date: Sun, 16 Sep 2001 13:48:51 +0100
> From: Ian Ibbotson <ian.ibbotson@k-int.com>
> The real need for sort to be close to search-request is, as the doc
> says, for targets that need to be able to optimise the way they
> work. I have a few SQL backends, and it's really inconvienient to
> execute what can be a heavy SQL statement, only to have to
> immediately re-evaluate it because a sort-request has just come in
> and now we need to tag some order by clause on the end.

This is purely an implementation issue, isn't it?  Your server can
implement this stuff however it likes.  For example, when you get a
search request, do nothing but remember what the request was, and
return a "success" indicator.  You need only actually submit the SQL
query when the user either (A) sorts the result set (in which case you
can include the ORDER BY clause) or (B) presents some records, in
which case that's a great moment to actually do the search.

	``Mmmm ... laziness.  Is there _anything_ it can't do?''
	       -- Homer Simpson, paraphrased.

 _/|_	 _______________________________________________________________
/o ) \/  Mike Taylor   <mike@miketaylor.org.uk>   www.miketaylor.org.uk
)_v__/\  "Good luck, everyone" -- Bob the Angry Flower after the WTC
	 disaster.  See http://angryflower.com/septem.gif
Received on Monday, 17 September 2001 07:21:11 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:26:03 UTC