Re: about context parameter

On Tue, Nov 05, 2002 at 10:06:19PM +0200, Nuutti Kotivuori wrote:
> brane@xbc.nu wrote:
> > The discussion blocked some time ago when it seemed that adding a
> > context param would be expensive. Later on I suggested storing the
> > context in the top-level pool (which would be different for each
> > client thread), but there haven't been any replies yet. Serves me
> > right for pushing comments into the issue tracker instead of posting
> > them here. But maybe I should just implement that...
>
> Well, I was kind of waiting for the discussion to sort itself out
> after a while - but then it happened to die off altogether.
>
> I'm also interested in seeing the context parameters appear in the
> code. :-)

I believe we should have something like svn_client_t. That object would be
opaque and could hold a number of things:

* auth info
* config info
* notification funcs?

It should be documented that it is totally fine to mix and match
svn_client_t structures in case a person wants to use different notification
functions, for example. To make it apparent that we aren't storing state in
the context (thus, they can be mixed/matched), we might actually want to
make the structure non-opaque.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org