RE: RE: Summary: URL rev proposals
From: Steve Dwire <sdwire_at_pcsigroup.com>
Date: 2003-08-14 16:52:37 CEST
(Posting in honor of a personal Lurker Day :-)
One side-effect of the "Redirect" approach, however, is that if I follow a link to the PUBLIC (...?rev=... or whatever) URL in a web browser, the redirect will send the browser to the PRIVATE (.../!svn/bc/...) URL *before* I have a chance to bookmark the page. If other clients follow the same convention (if other clients even have the "bookmark" concept...), then users will have to make a conscious and painstaking effort to get their bookmarks in the format we desire. It will be much easier for users to do the *wrong* thing (bookmark the private format) than it will be for them to do the *right* thing (bookmark the public format).
We can preach to the users the importance of not bookmarking the !svn syntax all we want, but there's not a very good chance the message get through to everyone. If bookmarking the private syntax is intuitive and mindless, and it initially seems to work, while bookmarking our preferred syntax takes additional knowledge, thought and effort with no immediate perceived benefit, a large percentage of the bookmarking population will have the !svn bookmarks whether we want them to or not. And they won't even know that they're wrong!
Though I REALLY LIKE the redirect idea, I think we need to be aware that redirecting like this really makes our "private" syntax at least as visible as the public syntax -- possibly more visible, depending on the behavior of the client software.
S_E_D
-----Original Message-----
> From: François Beausoleil [mailto:fbos@users.sourceforge.net]
> Hi !
> So, this means that I can bookmark a /!svn/bc/ URL, and send it to
Well, if you like to [snip] off the 'No' I put there, then yes.
Sander
---------------------------------------------------------------------
---------------------------------------------------------------------
|
This is an archived mail posted to the Subversion Dev mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.