Hi,
I have been trying out SVN as an alternative to CVS
and been very impressed. I have been using WebDAV
under Apache to remotely access my repository and it
has worked like a dream. I am now thinking of some
further work that needs doing for a customer of mine
and thinking about how best to layer (if indeed I need
to) WebDAV and SVN.
Here is a simple scenario - I have an XML file which I
want to be edited by both myself and my customer. I
host the file on a WebDAV enabled server so that my
customer can use JEdit with it's WebDAV plugin to
modify the file. WebDAV gives me basic versioning.
I now want the file to be properly versioned ( in the
context of a broader use case and true CVS/SVN type
capabilities) - so I put place it in an SVN
repository.
Do I now need to get my client to use an SVN client to
get the file and commit it back or can I somehow
continue to allow them to use a WebDAV client?
The ONE advantage of being able to use WebDAV (as far
as my relativly limited experience goes) is that I can
exclusively lock any given file to implement a fairly
basic workflow process - e.g. the file is currently
being worked on by my customer so none of my team
should make any changes until the file comes back and
the lock is removed. I don't beleive I can lock a
specific file in an SVN repositiory but someone may
correct me on this.
What is the best strategy for this collaborative
production scenario?
Best regards
Jeremy Aston
___________________________________________________________
Yahoo! Messenger - Communicate instantly..."Ping"
your friends today! Download Messenger Now
http://uk.messenger.yahoo.com/download/index.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 18 13:12:01 2004