[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: client api not optimal

From: Ich selbst <ichselbst_at_gmx.ch>
Date: 2002-08-25 21:30:22 CEST


> You can always set the baton to NULL if you don't want to use it.
> Subversion depends on APR, your application is going to link against
> APR, so using APR types doesn't seem unreasonable.
Only if you compile the complete source of Subversion for the client. But
I hope that there will be compiled libraries to link to for clients. And
you would need not just one but many many header files to include
(and look through if you don't use C or C++ and can't include those headers

> [snip]
> > - instead of the auth_baton use 'username' and 'password' - thats more
> > understandable
> When you call svn_client_checkout, say, you do not know if a username
> or password is required. Do you intend to always prompt the user for
> these, even if they are not required? Isn't that a little primitive?
> The point of the auth_baton is that if the data are not required then
> there is no need to provide them.
I don't want the user to enter those every time, but once. And then store
those during a whole session.
And if you don't want to use those, like you mentioned above: "You
can always set the <replace baton with authentication> to NULL if
you don't want to use it.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Aug 25 21:31:08 2002

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.