On Wed, 2003-06-04 at 05:10, John Locke wrote:
> As a web developer, I disagree. As Greg states, the query string implies
> that there is *one* resource receiving different query values. In a web
> development setting, the "resource" might be a script that then goes to
> retrieve different content based on the query string.
But remember, a resource may not exist at certain revisions. Does
it make sense to return a 404 because a query modifies what revision
of a resource you're asking for, but a plain request for the resource
itself returns a 200?
What you're actually asking the repository for is a revision of the
tree, and then a particular resource within that tree (i.e. the
tree is the *first* thing to be found, from the revision number).
Going to the resource first, then moving backwards, is, well, backwards.
I'd argue that a resource at a different revision is actually a
different resource (i.e. the object resides in a different tree
revision in the SVN filesystem). Each revision that bumps the
repository version creates as many new resources as there are objects
in your tree. The fact that SVN only stores changes is irrelevant.
The model is that there is an entire new tree to browse (that looks
mostly like the last one) that needs to be specified as part of the
resource you're looking for.
daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 4 01:43:00 2003