Subversion VS general DeltaV server/client

Hello,

I'm planning to design a general DeltaV client, since svn doesn't work against a general DeltaV server.

The general DeltaV client, dvc(DeltaV client) will have several version control commands like svn or cvs:

  - dvc import
  - dvc checkout
  - dvc commit
  - dvc update
  - dvc branch
  - dvc merge
  - dvc add
  - dvc delete
   ...

I have several questions to design the general DeltaV client.

I think basic commands(import, checkout, commit and update) could work with
server that support only basic versioning(linear versioning). Subversion
uses MKACTIVITY and MERGE to checkout(commit) and do you think we can
implement the basic commands without MKACTIVITY and MERGE support which are
advanced versionig package methods.

Also subversion expects some custom features from the server and the
subversion server is not a general DeltaV server.

Is there any reason that subversion uses some custom features?

I appreciate your help.

--
Sung Kim hunkim@cse.ucsc.edu
http://www.cse.ucsc.edu/~hunkim
Dreams become reality!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org