2013-01-23 09:20 AEST by Arthur Barrett - enhancement request for the client: version non-file assets, e.g.: http, caldav, carddav, email

The CVSNT client exclusively versions things that are 'on the client' and in particular things that are 'in the 
file system' or more specifically: 'in the current working directory (tree)'.

But what about things that are 'accessible' from the client?  e.g.: a web page, or an email.

I think it needs several elements to work really well:

1) some standard notation for add/commit, e.g. "import -x"
  cvs add -x http://www.mcgrath.com.au/171128
  cvs add -x https://docs.google.com/document/d/1CFmmKyOwWegXep
  cvs add -x <uri-path-to-caldav>
  cvs add -x <uri-path-to-carddav>
  cvs add -x email-subject/message-id
  cvs add -x oracle:instance/object-name

   note: some property on the versioned item (RCS level property) would need to store the 'real' URI.

2) some standard notation for where in the repository these are stored, e.g.:
   /http
   /caldav
   /outlook
   /oracle

3) some mechanism and standard notation to 'diff' these to the 'current' item, e.g.:
  cvs rdiff -x http/www.mcgrath.com.au/171128

   note: some property on the versioned item (RCS level property) would need to store the 'real' URI.
   note: to do a 'graphical' diff (eg: with winmerge) a 'checkout' API will also be needed...

3) some pluggable API so that us (and 3rd parties) can add support for new items, e.g.: sql server objects, 
oracle objects, outlook objects, lotus notes objects, http, caldav, carddav, etc.

3) integrate with some 'active' monitoring tool so that if the 'source object' changes it can be detected.