Re: Optional text base design discussion?

Michael Brouwer wrote:
> John, I'm well aware as to what svk does (I'm an svk comitter).

And I thought your name sounded familiar... ;-)

> Think of this cache as a subversion repository with obliterate-like
> functionality. Obviously this idea would need to be fleshed out more,
> but I do believe this could be implemented in a way that unifies the
> benefits of both svn and svk, and even let's users check out working
> copies of large projects without the need for a second local copy of the
> entire tree at all.

I think it might be easier to describe this feature as a caching proxy service.
 If all repository-to-WC activity occurred through a specially designed proxy,
and the Subversion client library was aware that it was being proxied, then you
could have a tunable cache which would automatically retrieve and cache the
text-base files as you needed them. I don't thing you would want to strictly
limit the cache by size, since a single very large binary file could exceed the
storage (of course you could also mark binary files as uncacheable).

Checking out files would be a transparent proxy to the original repository.
Executing diff or checking in files would transparently retrieve the text-base
from the server (if needed) and cache it for later use (you could also tune the
proxy to cache the files during checkout in order to have a fully local cache,
say for multiple overlapping WC's).

Does that seem like a different way to approach your proposal?

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