JADE Processing of an HTML Client Request

When the JADE system receives an HTML client request, the following actions are performed.

  1. The TCP/IP address and the contents of a hidden field containing the encrypted session identifier are obtained from the input data.

  2. The TCP/IP address and the encrypted session identifier are used to search the session dictionary for an existing session object for the client. If the entry is not found in the dictionary, a new client session object is created.

  3. A processRequest method of the WebSession class instance is then called, passing the request data to JADE. This method processes the request, and sends a formatted HTML page back by the named pipe or TCP/IP instance on which the input data was received.

    The jadehttp library sends this page to the client, and the Web server is then informed that the request processing is complete.

If you want to change the number of seconds after which Web-enabled applications wait for message transfers to complete before timing out, specify the ReadTimeout parameter in the [WebOptions] section of the JADE initialization file with the appropriate number of seconds. The default value is 600 seconds (10 minutes) but you can specify this parameter and set it to zero (0) if you do not want the Web-enabled application to time out waiting for message transfers to complete. (You can prefix this parameter with the name of the application if you want different applications to have different message transfer timeout values.)

You can use the MaxMessageSize parameter in the [application-name] section of the jadehttp.ini file to specify the maximum size allowed for a single-part Web message (that is, a single stream of data with minimal formatting) if you want a value greater than 1,000,000 bytes. (For details, see "Configuring JadeHttp for Remote Connections", in Chapter 2 of the JADE Installation and Configuration Guide.)

When you specify a maximum number of queued entries (which can be done using the MaxInUse[n] parameter in the [application-name] section of the jadehttp.ini file), any additional request received that would also be queued when the maximum queued entries is reached will be rejected. The user will be sent the contents of a file named busy.htm from the same directory as the jadehttp.ini file (as it is for the jadehttp.htm error file, described in the following section).

If that file is not available, the following text response will be sent. 

The application is too busy

This request cannot be processed at this time due to heavy usage - please try again shortly.

You can use the MinMessageSize parameter in the [application-name] section of the jadehttp.ini file or the MinMessageSize directive in the Apache mod_ jadehttp.so library to specify the minimum size allowed for a Web message received from JADE using the WebSession class reply method to send HTML string Web requests back to the client node.

The minimum value is 1 byte, the maximum value 1024 bytes, and the default value 10 bytes. This value is read the first time the specified application is accessed after jadehttp.dll has been loaded by Internet Information Server (IIS) or it is read once, when the Apache Web server starts.