[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Venti as storage backend

From: Enrico Weigelt <weigelt_at_metux.de>
Date: Fri, 13 Jun 2008 18:44:04 +0200

Hi folks,

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

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
* 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 ?


 Enrico Weigelt    ==   metux IT service - http://www.metux.de/
 Please visit the OpenSource QM Taskforce:
 Patches / Fixes for a lot dozens of packages in dozens of versions:
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-06-13 18:45:00 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.