Re: how to deal with HUGE repositories?
On Tuesday 16 November 2004 00:57, Subversion Newbie wrote:
> The reason why we need "svn update" to be really fast
> is: after a user "checks in" a modified file, she'll
> want to view it through the website very shortly
> afterwards. If there is a substantial delay (let's
> say more than 4 seconds after commiting the changed
> file) then we'll have complaints. These expectations
> are based on the current way of doing things, where
> users change files on what is basically a live
> website. (Not a pretty sight, huh?)
That is trivial if you use Apache2/WebDAV as server protocol.
Let's assume your repository is https://mydomain.com/svn/site1/trunk
...tell your users to enter just this URL into their browser to have an
online preview. The "GET" request issued by a normal browser is identical
to what subversion issues to get the newest version, so you always see the
newest version of your repository if you look at it with a normal browser
instead of subversion.
Received on Wed Nov 17 14:31:07 2004
- application/pgp-signature attachment: stored
This is an archived mail posted to the Subversion Users