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

Re: permanent solution for deltification problem (issue #1601)

From: <kfogel_at_collab.net>
Date: 2003-12-03 00:06:12 CET

mark benedetto king <mbk@lowlatency.com> writes:
> I agree that your proposal is more efficient in the APR_HAS_FORK
> case, but there are a few potential drawbacks that I'd like to point
> out:
>
> 1.) Trivial duplication of code between svnadmin's subcommand_deltify().
> One might say that this is "tight coupling", and that we should
> keep the system "modular".

The code duplication should be very minimal. The under-the-hood
interface is the same.

> 2.) Increased complexity of implementation.

Again, minimal (if it turns out not to be minimal, then I'll happily
go the other way).

> 3.) This is just FUD, but there may be some gotchas associated with
> forked BDB access that would not appear if the deltify happened in
> a brand-new process.

This is just FUD :-).

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Dec 3 00:52:28 2003

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.