Dealing with time out failures
It is possible that a data interface command, especially a GET command, can take a significant amount of time. One effect of this is that, by the time the response is available, the HTTP socket connection between the client application and Web User Interface server could have expired. To avoid this situation, the Web User Interface server can respond early with a status of TIMEOUT, while continuing to process the original request.
To retrieve the results of the original request, the client application should reply to a TIMEOUT response by sending another request to the server. On this new request, the client application specifies the TIMEOUTTOKEN query string and value taken from the TIMEOUT response. If the server receives a request with a TIMEOUTTOKEN, it either sends the response built for the original request or, if it is still not ready after a further period of time, sends another TIMEOUT response.