blob: 07b7f11e811e9e98ec529514eb3e7e80f3a970d4 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
|
httpd::content::scgi
=============
Back to: [Index](index.md) | [Package httpd::content](content.md)
The SCGI handler farms out the generation of content to an external process
running at a known port. Because this process is persistent, the SCGI system
avoids the overhead of spawning and spooling up an external process with
every page view.
To implement an SCGI handler, replace the **scgi_info** method with one
that will return a list containing the following:
SCGIHOST SCGIPORT SCGISCRIPT
* SCGIHOST - The hostname or IP address of the server running the process
* SCGIPORT - The port to connect to
* SCGISCRIPT - The SCGISCRIPT parameter which will be passed to the external process via headers.
The **scgi_info** method also makes a handly place to spawn a locally hosted process on demand.
For an example of this, see the [docserver.tcl](docserver.tcl) Example.
|
