Re: svn commit: rev 5119 - in trunk/subversion: svnadmin include libsvn_fs tests tests/libsvn_fs tests/clients/cmdline/svntest libsvn_repos
From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2003-02-27 05:41:45 CET
Philip Martin <philip@codematters.co.uk> writes:
> Now if the core, generic code is to add these parameters to the
Hmm, that's a good point. By stuffing all runtime parameters into a
> [...] assume that for some reason I cannot use my provider specific
Alas, I think your dream of putting the realm-data directly into the
> If the provider specific code cannot do it, then the core, generic
Right. True. These are all assumptions behind the current
In the current design, the way to implement a new auth provider is
1. write a provider that wants certain input data, and returns
2. find some place in the "core" svn code that receives the input
example1: only svn_client__open_ra_session() has the directory
example2: libsvn_ra_dav contains neon callbacks that
So the truth here is that it's usually impossible to write a "totally
Rather than propogate every single provider's baton down into various
So the only debate here is whether the auth_baton should contain a
> It's not a "Union of All Possible Runtime Values Not Known At Startup,
But those are *exactly* the same things.
"set of parameters that svn core code is forced to understand"
See?
Here's my only argument for using a hash instead of a structure:
My worry is that every time somebody wants to write a new provider,
---------------------------------------------------------------------
|
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.