CGIPLUSCALLOUT.C

Usage count: 1

This script provides a simple demonstration of the CGIplus callout facility, used to suspend normal script output and communicate directly with the server. This allows the script to request information from the server, or set certain script operating parameters, etc.

To begin an callout the CGIPLUSESC environment variable (logical name) is output as a record. For this script it has a value of:

  $E-FAFD6927446B2F3C6A76DF0D-

(but of course is not static, and varies each time the script is first executed).

A single-record script request followed by a single-record server response dialog may then be engaged in.

To end an callout the CGIPLUSEOT environment variable (logical name) is output as a record. For this script it has a value of:

  $D-A3245870D50881B18816D7BE-

(and also will vary each time the script is first executed).

Normal script output (to the browser) is then resumed. When in callout mode one or more request/responses may be made. Normal and callout output may be interleaved during a script response, as this script illustrates.

Example Behaviour

Translating a URL-style path to a VMS file specification:
```
  /wasd_root/src/httpd/
```
The request sent to the server was:
```
  MAP-PATH: /wasd_root/src/httpd/
```
The full server response was:
```
  200 wasd_root:[src.httpd]
```
Yielding a file specification of:
```
  wasd_root:[src.httpd]
```
Now a translation of a VMS file specification into a URL-style path:
```
  WASD_ROOT:[SRC.HTTPD]
```
The request sent to the server was:
```
  MAP-FILE: WASD_ROOT:[SRC.HTTPD]
```
The full server response was:
```
  200 
```
Yielding a path of:
```
  
```
Finally an error response to an unknown callout request:
The request sent to the server was:
```
  UNKNOWN?: WASD_ROOT:[SRC.HTTPD]
```
The full server response was:
```
  400 Unknown request
```

Comments

Success responses begin with an HTTP-like "200", other responses with appropriate status codes.