On Thu, May 22, 2008 at 07:33:20PM -0400, Mark Phippard wrote:
> On Thu, May 22, 2008 at 4:09 PM, <epg_at_google.com> wrote:
> > "Mark Phippard" <markphip_at_gmail.com> writes:
> >> On Thu, May 22, 2008 at 3:48 PM, <epg_at_google.com> wrote:
> >> > "Mark Phippard" <markphip_at_gmail.com> writes:
> >> >
> >> >> If we wanted to support it in JavaHL for people in single-threaded
> >> >> environments I would need an easy way to disable it from Subclipse as
> >> >> the JVM crashes hard and fast as soon as that code gets executed.
> >> >
> >> > Just don't put that one in your auth providers list?
> >> That level of detail is not exposed to the JavaHL consumer.
> > That is unfortunate. Is the entire client context filled in for
> > you, or only this part? How would you implement a configuration
> > option to disable certain auth providers?
> Since I work via JavaHL, I do not necessarily know what the context
> is. But I believe it includes things like the callbacks for
> authentication prompts and notification handlers. Those are things we
> can provide.
In the command line client, providers are initialised in
libsvn_subr/cmdline.c, more precisely in svn_cmdline_setup_auth_baton.
It uses the svn_auth_get_*_provider functions to get the providers
it wants, puts them in a list, and passes that to svn_auth_open.
Doesn't JavaHL provide the svn_auth API? If it does not,
shouldn't JavaHL be extended so Java-based clients can handle
auth providers the same way the command line client does?
Received on 2008-05-23 12:20:11 CEST
- application/pgp-signature attachment: stored