REQUEST_RESULT (for an application)

Time out (in seconds) for pending transactions.

The Request Result timeout is used to inform the user when a transaction is taking longer than expected. The REQUEST_RESULT element specifies the number of seconds to wait for the DVM to give an answer to the Application Server, after which the Application Server sends a "transaction pending" page to the front-end to inform the user that this transaction is taking longer than expected. This is also known as sending a keepalive response. The default transaction pending page automatically submits a new request to wait for the DVM to complete its processing.

Under normal operations, the front-end client sends a GET request to the Genero Application Server immediately after receiving a response. Meanwhile, the Genero Application Server stores data sent by the DVM for the application in its buffer, waiting for a GET request from the client. When the GET request is received by the Genero Application Server, if the server has data sent by the DVM in its buffer, the stored data is sent back to the front-end. If the DVM does not have data to send, the Genero Application Server waits and, if the DVM is still processing the request after the specified REQUEST_RESULT timeout expires, it sends the keepalive response to the front-end client and resets the REQUEST_RESULT timer.

Tip: The number of seconds specified for the REQUEST_RESULT timeout should be less that the cgi timeout. By default, the Apache Web server has the cgi timeout default to 300 seconds. Therefore, the REQUEST_RESULT timeout has an initial default setting of 60 seconds.

Usage example

<REQUEST_RESULT>60</REQUEST_RESULT>

In this usage example, the Request Result timeout is set to 60 seconds.

Parent elements

This element is a child of one of the following elements: