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

Re: Context parameter in public API

From: <cmpilato_at_collab.net>
Date: 2002-10-18 01:37:24 CEST

Nuutti Kotivuori <naked@iki.fi> writes:

> Firstly - about the configuration file in general.
>
> I think the configuration file should be a feature of the command-line
> client only. Ofcourse a Subversion library can provide access to a
> common configuration file, but the "svn_client.h" functions should not
> internally use the configuration file. Instead, some configuration
> parameter should be given to them. Someone mentioned a lot of good
> reasons already - but basically I think this is correct because
> there's going to be quite a few places where different clients are
> going to be wanting to store their configurations.

We specifically made a config-for-all so that not every client would
have to implement the exact same things over and over again, like
proxy values. That just puts a burder on client developers. So I
think we should let all the client use our configuration files, and
just encourage the developers of those clients to protect their
client-specific stuff with some sort of namespace-protected sections,
like [rapidsvn-general] or [gsvn-general].

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 18 01:40:06 2002

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.