On Tue, 2003-06-03 at 16:41, Daniel Patterson wrote:
> 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?
>
Well, there's the example of the svn update command to emulate--I don't
see that it needs to behave any differently.
> 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 see your point, but this is an implementation detail. Seems to me that
if you actually want to see an earlier version of a file, then you ought
to be able to put together a simple URL with a query string to do it.
When you view a directory, it also seems to me that it shouldn't be
difficult to append the query string to each of the links in the
directory, so you can browse the revision to see all the files.
I still don't see why this is a bad thing.
> 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.
Again I see your point, but I'm coming at this from a user perspective,
not a developer perspective.
What I'm looking to use Subversion for is to store different versions of
files--contracts, documents, marketing material, etc. Not source code.
The simple fact that Subversion does binary deltas already makes it one
of the best version control systems for this use. Providing easy
integration with a web server is the other compelling feature that has
made me a Subversion fan. And being able to request a revision based on
a date--Super!
I just hope that any URL scheme the project chooses to implement for
accessing different versions in the repository follows existing
conventions, rather than creating new ones. And being a web developer, I
prefer web conventions...
Cheers,
--
John Locke
http://freelock.com
Recently published: "Extend the reach of users' email with IMAP"
http://www.techrepublic.com/article_guest.jhtml?id=r00620030507jxl01.htm
Play sports? Check in at http://teamcheckin.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 4 08:09:31 2003