I have a WCF client that connects to the server in intranet The first call takes important time and the user patiently waits Unless it is complete Second, the third call is at least 30% faster.
What is the best practice to keep WCF clients ready to call? I am thinking of background thread which can be used from time to time pings server (or for the very first time the application can be started), but what could be better / simpler ways?
The service is hosted with IIS6 wsHttp (dual) binding problem with the double endpoint is critical
This behavior may be related to the fact that the application pool in IIS does not load into memory, the first request comes.
Comments
Post a Comment