Greg Stein wrote:
> On Fri, Oct 11, 2002 at 02:37:15PM +0300, Nuutti Kotivuori wrote:
>> Roughly as pseudocode:
>>
>> svn_error_t *svn_client_context_open(svn_context_t **ctx);
>>
>> svn_error_t *svn_client_context_close(svn_context_t *ctx);
>
> The open would take a pool, and the close would be implied by
> clearing or destroying that pool. (that's the typical pattern of use
> in SVN)
Ofcourse, thanks.
>> And in usage, for example:
>>
>> svn_error_t *
>> svn_client_ls (apr_hash_t **dirents,
>> const char *url,
>> svn_opt_revision_t *revision,
>> svn_client_auth_baton_t *auth_baton,
>> svn_boolean_t recurse,
>> apr_pool_t *pool,
>> svn_context_t *ctx);
>
> The auth_baton would be incorporated into the context.
>
> If people wanted multiple auth within a single app, then they can
> use multiple context objects. Or maybe the context has a way to
> change auth values.
Yes, this sounds reasonable as well.
>> Is the 'config' file a feature of svn_client libraries or is it
>> something that only the command-line client uses?
>
> The config file is one way to store options. The context should be a
> generic mechanism for passing option state. A GUI app might actually
> store all that stuff within its own state files.
What I had in mind as well.
-- Naked
---------------------------------------------------------------------
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:16:02 2002