API Login

Post your questions regarding using the Vault and Fortress API in your programs.

Moderator: SourceGear

Post Reply
DaveA
Posts: 4
Joined: Mon Dec 07, 2009 9:01 am

API Login

Post by DaveA » Wed Jan 20, 2010 2:51 pm

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.

jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Re: API Login

Post by jeremy_sg » Wed Jan 20, 2010 4:49 pm

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?
Subscribe to the Fortress/Vault blog

DaveA
Posts: 4
Joined: Mon Dec 07, 2009 9:01 am

Re: API Login

Post by DaveA » Thu Jan 21, 2010 6:51 am

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.

jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Re: API Login

Post by jeremy_sg » Thu Jan 21, 2010 8:39 am

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

Post Reply