Go to the first, previous, next, last section, table of contents.
The explanation is much clearer if we begin with an example. Imagine that a cgi-bin action, named New entry in catalog, does the following:
The first two actions may be performed by an existing cgi-bin action, the one in charge of proposing an insert form to the user and insert the record in the database, See section Record insert form (sinsert_form). When designing the New entry in catalog action, we first want to call the Record insert form action, then perform the third action (link record at the current point of the catalog) using the record just created.
Simply put, a recursive CGI call occurs when a cgi-bin make use of another cgi-bin action to perform its action. From the user point of view, the action that makes use of recursive CGI is always a multi step interaction process.
The cgi-bin parameters that are visible in the URLs and are related to the recursive calls are the following:
When a cgi-bin behaves in a different way if called recursively, it will base it's action on those tags.
Go to the first, previous, next, last section, table of contents.