Re: Configuring encrypted password caching: API proposal

On Thu, Oct 16, 2008 at 10:17 AM, David James <james82_at_gmail.com> wrote:
> Right now, our API for configuring encrypted password caching is
> rather difficult to use. Right now, user applications which want to
> use encrypted password stores must configure their application to load
> different libraries and call different functions depending on what
> password stores are available. I think that we should simplify our API
> so that users can use encrypted password stores without writing their
> own code to dynamically load the appropriate libraries.
>
> The simplest possible API for loading encrypted password stores would
> be an API that simply allowed users to specify the type of the
> provider they want, and then we would return the provider if it is
> available.

...

> Thoughts?

I like this idea as well and I can attest to the complexities that
having multiple approaches has. The SWIG bindings and ctypes-python
bindings are directly impacted by our current approach, often ending
up in either ignoring Subversion functions in the bindings or having
to do magic to make sure things end up in the bindings appropriately.

+1

-- 
Take care,
Jeremy Whitlock
http://www.thoughtspark.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org