W3C home > Mailing lists > Public > www-webdav-dasl@w3.org > April to June 2002

RE: comment on issues in DASL draft: truncation

From: Julian Reschke <julian.reschke@gmx.de>
Date: Wed, 29 May 2002 08:37:02 +0200
To: "Jim Whitehead" <ejw@cse.ucsc.edu>, <www-webdav-dasl@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCIEMDEKAA.julian.reschke@gmx.de>

> From: www-webdav-dasl-request@w3.org
> [mailto:www-webdav-dasl-request@w3.org]On Behalf Of Jim Whitehead
> Sent: Wednesday, May 29, 2002 2:49 AM
> To: www-webdav-dasl@w3.org
> Subject: RE: comment on issues in DASL draft: truncation
>
>
> > I agree that this could be useful, but I think this issue should be
> > consolidated with issue JW5 (see below), which proposes that DASL
> > basicsearch ought to have a way for client to request additional result
> > sets.
>
> I've been starting to think that the result from a SEARCH should
> be both the
> requested results and a URL where the query results can be found later. It
> would be tricky, but not impossible for a server to maintain these query
> results for a small period of time, and would open up several
> possibilities,
> such as requesting partial results via a GET range request, proxy
> caching of
> query results, etc.  Servers could advertise the duration of the
> validity of
> the response using HTTP caching headers.
>
> Thoughts? Do I need to flesh this proposal out more?

I think this is indeed the key to implement some of the requested features.
So, if you have some good ideas, go on!
Received on Wednesday, 29 May 2002 03:07:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 22 March 2009 03:38:08 GMT