Contents of this section
- To uninstall WebKit, simply erase the following
files. These are only their most common locations, so your
commands may be a little different.
- /usr/local/include/webkit.ch
- /usr/local/lib/libwebkit.a
- /usr/local/etc/httpd/cgi-bin/webkit
- /usr/local/etc/httpd/cgi-bin/webkit-gateway
- /usr/local/etc/httpd/cgi-bin/example\1-9\
- /etc/webkit.conf
- WebKit examples directory
Remove a webkit-specific entry from /etc/syslog.conf if
needed.
- If your WebKit program blows up with no visible signs of an error
code--look to issues with the startup code, which executes before WebKit's
error handler kicks in. You might be getting a "user limits exceeded"
error as a result of running some other FlagShip application at the
same time as your WebKit application under a single-user runtime
license.
- When you start your WebKit program from the command line, it will
go into the background and await connections on the specified port as a
Gateway-mode server. If you do not want this behavior, compile in your
own
main()
function and you will be in control.
- Your <FORM> tags should use METHOD=POST.
- If you put a protocol analyzer on the WebKit host you'll find this
traffic passing from the Gateway process to the server:
4 bytes length of environment variable block
4 bytes number of environment variables
n bytes environment variable block:
name -NUL- value -NUL- ...
4 bytes length of form variable block
4 bytes number of form variables
n bytes form variable block:
name -NUL- value -NUL- ...
The Gateway process takes whatever it gets back over the same socket
(presumably HTML code) and shoots it to standard output, which
CGI passes to the browser.
- It is possible, when you build your program with a FlagShip compiler that
is not licensed for unlimited users for some other FlagShip
application to be running on the host when your application is invoked.
This is a major problem because you get an
alert()
box that
reads, "Sorry, user limits exceeded" before
the WebKit initialization code gets a chance to set a different
errorblock()
from FlagShip's default. When linked with
libwebkit.a
, then, alert()
just sits there and waits for a
keypress that will never occur. The only thing to do is to kill the
process.
- When using a batch mode program from a terminal you may wish to
execute
stty sane
afterwards. Otherwise the FlagShip runtime
messes with your terminal settings. This is not necessary when
launching a Gateway mode server because libwebkit.a does this for you.
Next Chapter, Previous Chapter
Table of contents of this chapter,
General table of contents
Top of the document,
Beginning of this Chapter