Hi,
When using the ClientInstance.Get method of the VaultClientOperationsLib the returned VaultsStatusCode is often seemingly incorrectly returned as SuccessRequireFileDownload.
When I check the files that this code is returned on, they have actually been updated - so no further download is required. Could this be a bug? Or am I misintepreting the return code.
( Source Gear Vault version 4.1.1.18060,
VaultClientOperationsLib.dll 4.1.1.18060 )
Thanks,
Nick
Incorrect VaultStatusCode?
Moderator: SourceGear
-
- Posts: 3
- Joined: Mon May 12, 2008 10:03 pm
Hi,
Thanks for the response.
So you are saying that the SuccessRequireFileDownload return value does not mean that a further download is required, but instead that
files were downloaded during the Get action. Is that the correct intepretation?
This seems contrary to the response given in this post (look at last response) which says that if you get this status a download is still required.
http://support.sourcegear.com/viewtopic ... statuscode
Thanks
Thanks for the response.
So you are saying that the SuccessRequireFileDownload return value does not mean that a further download is required, but instead that
files were downloaded during the Get action. Is that the correct intepretation?
This seems contrary to the response given in this post (look at last response) which says that if you get this status a download is still required.
http://support.sourcegear.com/viewtopic ... statuscode
Thanks
Nick:
When you issue a GET request, an array of VaultRequestGetFile[] is sent within the request. The data in this request contains a two members Base and Target Object Versions of the file in question. Using these members, a client can control what is sent over the wire (deltas between the two, or an entire file if baseline is set to zero).
When the server receives the request, it looks up the file for the specified path. If the requested baseline version is the same as the version found in the tree, a GET is not really required since the BASE version the client matches the server. In this case, the Server sets the return code to VaultStatusCode.Success, and the client has not need to actually GET the file.
If the requested baseline version is different from the version found in the tree, the server will return VaultStatusCode.SuccessRequireFileDownload and prepare the file data to get the client's file to the target version.
HTH
When you issue a GET request, an array of VaultRequestGetFile[] is sent within the request. The data in this request contains a two members Base and Target Object Versions of the file in question. Using these members, a client can control what is sent over the wire (deltas between the two, or an entire file if baseline is set to zero).
When the server receives the request, it looks up the file for the specified path. If the requested baseline version is the same as the version found in the tree, a GET is not really required since the BASE version the client matches the server. In this case, the Server sets the return code to VaultStatusCode.Success, and the client has not need to actually GET the file.
If the requested baseline version is different from the version found in the tree, the server will return VaultStatusCode.SuccessRequireFileDownload and prepare the file data to get the client's file to the target version.
HTH
Jeff Clausius
SourceGear
SourceGear