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

Re: New library init requirement to support *new* functionality?

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2006-06-21 14:25:05 CEST

On 6/21/06, Branko ibej <brane@xbc.nu> wrote:

> Last I heard, if we compile with SASL, we don't need the old auth code,
> since SASL does it all for us. If that's still the case, what you
> propose is not an option.

Well, we can certainly change that... The SASL code isn't set in
stone, it's certainly possible to architect it such that the old code
is used as a fallback if the new code hasn't been initialized.

> And it's not an option in any case, because dynamically-linked clients
> built against the 1.3 libraries must work with the 1.4 libraries (it's
> not an issue for svnserve, we control that).

Why is that so? Assuming we make it such that the old code is a
fallback, old clients linked against a new set of libraries will
simply continue using the same code (and same functionality) as they
used to have, because they'll never call the init function.

> OF course, we do have this particular problem solved (at least the
> single-threaded initialisation part ...) in
> subversion/libsvn_fs_base/bdb/env.c: svn_fs_bdb__init. A lot better than
> svn_utf_initialise, because the BDB env cache really really has to be
> unique per process.

Naturally, that is another way to do things, and would avoid this kind of mess.

-garrett
Received on Wed Jun 21 14:26:00 2006

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