How does the version-url caching works

[Alexander Kitaev <al...@tmate.org>]

Hello All,

I'm developing java svn client library and got the following question
regarding commit over DAV implementation - I couldn't understand how
version-url caching works in svn client. Consider the following working
copy:

/directory
/directory/file.txt

Working copy is at revision 1 and root directory contains corresponding
version-url in its dir-wcprops file.
Now I modify file.txt and commit changes. File.txt version-url is changed,
cause appropriate information is received in merge response, so root and
directory version-url points to the revision 1 and files version-url points
to the revision 2. 

Now I would like to copy directory/file.txt to copy.txt. For this, during
commit, I have to checkout root of the repository to the created activity,
and I'm using cached version-url value (stored in the root's dir-wcprops) -
and of course get a conflict response. However real svn client works fine -
it just does not use cached version-url value, but re-fetches it from the
svn server. What I could not find is where svn client decides whether to use
cached vurl or refetch it.

Hope my question is more or less clear...
Thanks, Alexander Kitaev.

 

> -----Original Message-----
> From: Alexander Kitaev [mailto:alex@tmate.org] 
> Sent: Monday, October 04, 2004 4:42 PM
> To: dev@subversion.tigris.org
> Subject: RE: Pure java subversion library
> 
>  
> Hello Garrett,
> 
> > Interesting.  How far along is it at this point?  I see an 
> awful lot 
> > of code, how much of it is functional?  Does the
> There are two parts in the library: low level and high level. 
> 
> Low level part is more or less finished and provides the same 
> functionality
> as declared in subversion/include/svn_ra.h, i.e. it allows 
> one to perform
> all read and write operations on repository without creating 
> and managing
> working copy files. Svn, http, and https protocols are 
> supported, however
> https is limited by the java cryptographic support, I didn't 
> investigate it
> a lot, but with some sites ssl connection works fine and with some it
> doesn't work.
> 
> High level part provides an API similar to the javahl bindings and its
> default implementation works with the same working copy files 
> format as
> "native" svn library. Not all the methods are implemented but 
> there are
> already commit,update,import,export,copy,move and property management
> methods (all methods work with the wc files). Merge and status are not
> implemented yet. My milestone is to provide a command line 
> java client that
> will work using this library and will implement all the 
> features (or all
> useful features) of the "native" client. This way I will be able to
> bootstrap the library and make sure that it works in the reallife
> conditions.
> 
> There are unit tests and they all pass at the moment, so all 
> the declared
> API is functional at least to the level defined in the unit tests :)
> 
> I hope eventually all this information along with the javadoc 
> will appear on
> the website.
> 
> > eclipse plugin do anything useful at this point?
> There are two plugins. One just wraps the library and another 
> is a simple
> eclipse view that allows one to browse repository, view files 
> and their
> props, similar to the web svn browser with some more 
> information provided.
> It was tested with eclipse 3.1. To test the "browser" plugin download
> 01.10.2004 version, because latests version doesn't contain 
> it, only the
> wrapper plugin. This eclipse view plugin has very little 
> practical meaning
> and was written merely as a test app for the "low level" 
> functionality of
> the library.
> 
> Thanks,
> Alexander Kitaev.
> 
> > -----Original Message-----
> > From: Garrett Rooney [mailto:rooneg@electricjellyfish.net] 
> > Sent: Monday, October 04, 2004 4:04 PM
> > To: alex@tmate.org
> > Cc: dev@subversion.tigris.org
> > Subject: Re: Pure java subversion library
> > 
> > Alexander Kitaev wrote:
> > > Hello All,
> > > 
> > > I'm developing a pure java subversion client library. 
> > Library is not 
> > > finished yet, but some of the important features are 
> > already there, so 
> > > developers may use library in their applications. Latest 
> > source code 
> > > and binaries are available at http://tmate.org/svn/ Library is 
> > > distributed under the same kind of license as subversion itself.
> > 
> > Interesting.  How far along is it at this point?  I see an 
> > awful lot of code, how much of it is functional?  Does the 
> > eclipse plugin do anything useful at this point?
> > 
> > -garrett
> > 
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> > For additional commands, e-mail: dev-help@subversion.tigris.org
> > 
> > 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org