Asynchronous Server Requests

The ClientRequestTimeout Web Configuration parameter defines the default client timeout, >> ClientRequestTimeout. This timeout is also applied to a full synchronizations. It is often set to several minutes to ensure, that a full synchronization can be carried out.

This timeout also defines the time span until a "Server not available" error is generated if the server does not respond to a request.

If the user connects to the server using a VPN, the scenario that a network is available but a network connection is not established hardly occurs, therefore, a long timeout interval is rather annoying.

You can define that requests are handled asynchronously. Define a timeout for the server and a retry interval. If the request has not finished processing within the server timeout, the server informs the client about this pending request. The server checks after the retry interval whether the request was processed. If the request is still pending, the server re-checks regularly until the process has finished.

To enable asynchronous server requests, set the following Web Configuration parameters:

Note: If you set System.AsynchRequestWaitTime, you can assign the default value (60 seconds) or even a smaller value to the ClientRequestTimeout parameter. All synchronous server requests (including the synchronous part of asynchronous server requests) are carried out within this time span.