I am using the following to log in.
ServerOperations.client.LoginOptions.URL = url;
ServerOperations.client.LoginOptions.User = username;
ServerOperations.client.LoginOptions.Password = password;
ServerOperations.client.LoginOptions.Repository = repository;
ServerOperations.Login();
My question:
Is there a login that will not update the cache files.
The ServerOperations.Login() at times take up to 15+ seconds. I am assuming that that the login is also updating the CacheMember_Repository which grows very large with our database(s).
Thanks in advance.
API Login
Moderator: SourceGear
Re: API Login
No, there is not. We thought that a login that didn't do a refresh would not be helpful, since it would be out-of-date with regard to the server.
Would it be possible for your API app to just stay logged in?
Would it be possible for your API app to just stay logged in?
Subscribe to the Fortress/Vault blog
Re: API Login
My API runs a series of tasks that require different logins. I can see requiring the cache to be updated when running the Vault Client. But exceptions must be built in to accommodate other types of operations.
Re: API Login
It would help to get more specific information on what you're doing. Please email support at sourcegear.com ATTN: jeremy with a link to this thread.
Subscribe to the Fortress/Vault blog