W3C home > Mailing lists > Public > www-push@w3.org > July to September 1997

Re: Collections

From: Judith Slein <slein@wrc.xerox.com>
Date: Wed, 17 Sep 1997 10:32:18 PDT
Message-Id: <2.2.32.19970917173218.009b72f0@pop-server.wrc.xerox.com>
To: Arthur van Hoff <avh@marimba.com>
Cc: Judith Slein <slein@wrc.xerox.com>, w3c-dist-auth@w3.org, Push Workshop <www-push@w3.org>
Thanks for your background on the DRP index.

The current version of the WebDAV protocol specification, which includes
collections, can be found at:
http://www.ics.uci.edu/~ejw/authoring/protocol/draft-ietf-webdav-protocol-02.txt


>> I think what is really desirable for (2) is for the client to be able to
>> specify in an INDEX request what information it wants about the members of
>> the collection.  Collections are used for lots of different purposes, and
>> different properties of the members will be useful in different contexts.
>
>Right. That would be ideal.
>
>> However, this flexibility would make it impossible for the index to be
>> stored as a file, as DRP suggests -- it would have to be generated in
>> response to the client's request.
>
>I'm not sure why that is so. Couldn't you generate a file containing
>a DRP flavored collection? I would really like to stay away from
>defining
>new HTTP methods if at all possible.
>
Yes.  I was just looking for a single approach that would let you get the
DRP information about each member of the collection, or any other set of
properties for each member of a collection.  If you want it to be really
open-ended, letting the user-agent specify any set of properties it likes,
then you can't have a URL for each possible set of properties, so some
extension to HTTP will be needed.

--Judy
Name:			Judith A. Slein
E-Mail:			slein@wrc.xerox.com
Internal Phone:  	8*222-5169
External Phone:		(716) 422-5169
Fax:			(716) 265-7133
MailStop:		105-50C
Received on Wednesday, 17 September 1997 13:29:53 EDT

This archive was generated by hypermail pre-2.1.9 : Wednesday, 24 September 2003 13:16:30 EDT