On Dec 3, 2008, at 18:23, Ashish Utagikar wrote:
> So is there any plan to implement this feature in svn in the future
> or as you said since subversion is designed for low bandwidth
> situations, the developers are not going to do it.?
> Hi Bob,
> As Ryan explained when I meant data caching, i mean the
> client has to contact the repository everytime we do svn update,
> svn commit etc.. which might be a hit on the network bandwidth.
> Instead of contacting the repository evrytime, we can get the file
> changes from the cache which lies on the same machine/filesystem
By definition it would not be possible to implement "svn update"
without contacting the repository, since its purpose is to get new
changes from the repository. "svn update" is of course efficient in
that it only gets from the server the difference between what the
client has and what the server has; if they're already identical,
then very little data has to go over the network to determine that
(though it may take some time while the client figures out the state
of the working copy, depending on the size of the working copy).
Though again I encourage you to have a look at svk which is designed
even more for those wanting to work offline. I understand that it
lets you make commits to your own personal copy of the repository,
and then later send those back up to the main repository (assuming of
course there are no conflicts with commits others have already made
to the main repository).
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2008-12-04 01:29:43 CET