Next message: Clemm, Geoff: "http://dav.ics.uci.edu/vdt/draft-ietf-deltav-versioning-03.1.doc"
Message-ID: <65B141FB11CCD211825700A0C9D609BC0187997F@chef.lex.rational.com>
From: "Vasta, John" <jvasta@Rational.Com>
To: "'Tim_Ellison@oti.com'" <Tim_Ellison@oti.com>, ietf-dav-versioning@w3.org
Date: Wed, 23 Feb 2000 10:35:03 -0500
Subject: RE: Enumerating repositories and workspa
<tim>
The principle adopted so far has been that workspaces,
repositories, etc. are just resources, and can be managed in the URL
namespace however the
client chooses. The server is free to restrict the areas where these
resources are stored, but there is no 'meta'-area containing such resources.
</tim>
If the server is free to have restrictions, then how can clients discover
what the restrictions are? I don't see how clients can do much of anything
without knowing how to form URLs to resources, if there are restrictions on
the form of those URLs.
<tim>
As such there is no way for clients to discover all workspaces any more than
there is a way to discover all activities or configurations, etc. It is
unclear to me that the client should be shown all possible repositories in a
browser.
</tim>
But you can discover all activities, configurations, and versioned resources
in a given repository; there are special collections defined for them, and a
server is allowed to restrict those resources to be contained in those
collections. If a client cannot discover what the repositories are, how can
it specify the location of any of the resources which are in those
constrained areas?
John