Tag: Performance
-
A Quick Performance Tip
The below code will save you a round-trip for each of your Vault API web service calls. System.Net.ServicePointManager.Expect100Continue = false; If you have your own Vault client, you should put the code sometime during startup. If you are running inside an Vault client from Autodesk, this value should already be set to false. I don’t…
-
Web Service Invoke Events
The third type of event we introduced in Vault 2012 is the Web Service Invoke Events. The purpose of the Invoke events is to give you a single choke point for whenever your code invokes a web service call to the Vault Server.
-
Coding for Performance – Getting All Files
In my last Coding for Performance article, I explained the best way to get File objects from a set of File ID values. But what if you don't have the ID's? What if you want to get all the files in the Vault, and you don't have any information to start with? I came up…
-
Coding for Performance – Array Functions
Welcome to a new ongoing series which will be focusing on writing optimized Vault code. In may cases, there are multiple ways to get data from the Vault server, but some ways may be quicker than others depending on your needs. There are many factors in Vault performance. Network speed, server configuration, available memory, concurrent…
You must be logged in to post a comment.