Re: Optional text base design discussion?

Michael Brouwer wrote:
> Another option would be to locally store a text-base cache of some sort
> outside the actual working copies. This cache could be shared between
> multiple working copies of the same project tree. The text base cache itself
> could potentially use some kind of delta storage model to provide multiple
> cached revisions of files. That way not just svn diff and svn status could
> be local, but potentially diffing between trunk and a branch that are both in
> cache could be. The cache can be as sparse or as filled as a user likes,
> with the ultimate cache being a mirror of the entire repository, making every
> operation disconnected.

Congratulations! You've just reinvented SVK:

        http://svk.elixus.org/

Let's see:

1) stores the "text base" using a delta storage model - check (SVK has a
repository using delta storage to compare against);

2) shares the "text base" with multiple working copies - you can check out
multiple working copies from the same SVK repository;

3) sparse cache - check (SVK can mirror a remote repository in whole or from any
arbitrary revision).

;-)

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Blvd
Suite H
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org