Re: Context parameter in public API

cmpilato@collab.net writes:
> 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].

I think that's what Nuutti is allowing for. The idea is that our
library interfaces takes a context baton object.

One way to fill that object is to call svn_config_read_config(&object)
or whatever.

But another way is for some GUI client, say, to have its *own*
mechanism for filling the object. However, such a client is under no
obligation to fill the object its own way. It is free to just call
svn_config_read_config(&object) like our client does.

Whatever way it gets filled, the object is then passed down to the
client layer. If you pass NULL, you get default behaviors.

Make sense?

-K

---------------------------------------------------------------------
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:47:55 2002