- From: Matthew Dovey (LAS) <matthew.dovey@las.ox.ac.uk>
- Date: Tue, 20 Apr 2004 13:40:55 +0100
- To: "ZIG" <www-zig@w3.org>
> I think the most obvious solution, if you want to stay close > to what's in the current standard, involves a combination of > concurrent operations and > asynchronous resource control requests coming back from the > server. The > User Information format SearchResult-1 already provides most > of the data elements you would want to describe partial > search results, and if you use this together with resource > control, it seems clear to me that the intent is that the > client should be able to issue present requests on the > partial results, even before the final search response has > been received. The main limitation that I hit with this approach (and I think raised it at the time, so it will be in the archives of the ZIG list from about 1998/1999!) is that the SearchResult-1 format can return how many records per database but not directly whether database returned an error or time-out (i.e. you can say a databse returned 0 results but not whether that was an error or a real 0 results) (without using other mechanisms to query what that 0 results means). Matthew
Received on Tuesday, 20 April 2004 08:41:27 UTC