This REQUEST_RESULT element specifies the number of seconds the GASJGAS waits for the DVM to respond to pending
transactions.
Syntax
<REQUEST_RESULT>seconds</REQUEST_RESULT>
- seconds specifies the number of seconds to wait for a response from a
transaction request.
Child elements
There are no child elements.
Usage
You use the REQUEST_RESULT timeout to provide information to the user when a
transaction is taking longer than expected. After the timeout expires, the GASJGAS 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
keep-alive 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 sends a
GET request to the
GASJGAS immediately after a response. Meanwhile, the
GASJGAS stores data sent by the DVM for the application
in its buffer, waiting for a
GET request from the front-end. When the
GET request is received by the
GASJGAS, these conditions determine the response:
- 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 GASJGAS waits and, if the DVM is still processing the request after the specified
REQUEST_RESULT timeout expires, it sends the keep-alive response to the front-end
and resets the REQUEST_RESULT timer.
Important: The REQUEST_RESULT timeout has an initial setting
of 45 seconds. When configuring this setting, you must ensure it is less than the Common Gateway
Interface (CGI) timeout of the web server you are using.
See FastCGI Installation and Web Server Configuration.
Usage example
<REQUEST_RESULT>45</REQUEST_RESULT>
In this usage example, the Request Result timeout is set to 45 seconds. This is the default
setting.
Parent elements
This element is a child of the following: