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

RE: comment on issues in DASL draft: truncation

From: Wallmer, Martin <Martin.Wallmer@softwareag.com>
Date: Wed, 29 May 2002 07:49:13 +0200
Message-ID: <DFF2AC9E3583D511A21F0008C7E6210602D90234@daemsg02.software-ag.de>
To: "'Jim Whitehead'" <ejw@cse.ucsc.edu>, www-webdav-dasl@w3.org

That sounds very interesting. And I don't think its too complicated to
implement. However, I'd suggest to keep this idea for later, not for the
current DASL.

Martin

-----Original Message-----
From: Jim Whitehead [mailto:ejw@cse.ucsc.edu]
Sent: Mittwoch, 29. Mai 2002 02:49
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?

- Jim
Received on Wednesday, 29 May 2002 03:08:20 GMT

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