Venti as storage backend

Hi folks,

I'm currently thinking of using venti instead of the filesystem
as storage backend. For those who dont know it yet:

    http://en.wikipedia.org/wiki/Venti
    
My idea is to take the fsfs backend as template and change it
that way:

* some table list holds an mapping between mappings of the
  revision-IDs and venti keys.
* for reading, the venti key for some revision is fetched from
  that table and the file is downloaded from venti into a local
  cache.
* on commit, the new revision file is uploaded to venti and the
  returned key added to the table.
  
Everything else, IMHO, should remain the same.
(ah, perhaps the same w/ the revrops files)

What do you think about that approach ?

cu

-- 
---------------------------------------------------------------------
 Enrico Weigelt    ==   metux IT service - http://www.metux.de/
---------------------------------------------------------------------
 Please visit the OpenSource QM Taskforce:
 	http://wiki.metux.de/public/OpenSource_QM_Taskforce
 Patches / Fixes for a lot dozens of packages in dozens of versions:
	http://patches.metux.de/
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org