Proxy Mode


(coming soon)
On some systems, particularly those with limited memory or processor power, a FlagShip-compiled program may take more than a few seconds to startup before executing any programmer-supplied code. If your WWW server gets more than a little traffic, or if clients are seeing inordinate delays in receiving output from your Webkit-enabled server, you may be better off using "proxy mode."

In proxy mode, a CGI-enabled FlagShip program acts like a network daemon. Instead of being invoked directly by the HTTP server for each client request, it is started as a background process (just like a Usenet news server or database server) accepting connections from a shell script that is in turn invoked by the HTTP server. The difference is that the script can spawn multiple instances of the CGI-enabled FlagShip program to enhance performance by eliminating redundant execution of FlagShip startup code.

In proxy mode, it is the Webkit proxy program that is invoked directly from HTML; it passes the CGI input over a network socket to the CGI-enabled FlagShip program and returns the output back to CGI but does no intelligent processing itself.

wkproxy is installed in the cgi-bin directory with the sticky bit set to suggest to the operating system that it remain in memory for enhanced performance. By default, it uses the "well-known" TCP port 1153 to communicate with the CGI-enabled FlagShip program.

Next: Auxiliary System Functions
Previous: Direct Mode
Webkit Index