You need to sign in to do that
Don't have an account?
Dennis Baker
Instantiating the Salesforce Service object to use the API for the first time in a session takes approximately 15 seconds. Is there any way to reduce this time?
We have a .NET application that connects to salesforce via SOAP and uses the API for creating/updating objects.
We noticed the initial instantiation of a new Salesforce Service object for a new session takes approximately 15 seconds.
Has anyone else come across this issue and/or found a way to reduce this time significantly?
We currently use the Enterprise WSDL and I'm looking into downloading the Partner WSDL to see if this is what we should be using, but I wanted to check with the forum in case others have come across this issue.
Any help would be appreciated. Thanks.
We noticed the initial instantiation of a new Salesforce Service object for a new session takes approximately 15 seconds.
Has anyone else come across this issue and/or found a way to reduce this time significantly?
We currently use the Enterprise WSDL and I'm looking into downloading the Partner WSDL to see if this is what we should be using, but I wanted to check with the forum in case others have come across this issue.
Any help would be appreciated. Thanks.
If you don't want to switch to using a Web Reference have a look at How to: Improve the Startup Time of WCF Client Applications using the XmlSerializer (https://msdn.microsoft.com/en-us/library/aa751883(v=vs.110).aspx)
All Answers
If you don't want to switch to using a Web Reference have a look at How to: Improve the Startup Time of WCF Client Applications using the XmlSerializer (https://msdn.microsoft.com/en-us/library/aa751883(v=vs.110).aspx)
I'm reviewing the links you supplied. In particular the XmlSerializer option - this may be the one that helps our current environment.
We are using the Salesforce object as a Web Reference in our application.
If you are using a Web Reference, ensure you have compression enabled.