functions initialise a FastCGI context for
These functions will only work if invoked as FastCGI servers, for
They should be called as early as possible in the life-span of a FastCGI
application, preferrably directly after initialisation.
The collective arguments are defined in
Function arguments are not copied:
all pointers are passed by reference and used in later invocations of
The first form,
is for applications using the system-recognised MIME types.
This should work well enough for most applications.
It is equivalent to invoking the second form,
khttp_fcgi_initx(fcgi, kmimetypes, KMIME__MAX,
keys, keysz, ksuffixmap, KMIME_TEXT_HTML,
pages, pagesz, defpage, NULL, NULL, 0, NULL);
After invocation with a return value of
pointer is filled in (and must be later be freed with
functions may be invoked.
in accordance with the FastCGI specification,
will install signal handlers for
These should not be changed by the calling application, but are not
prohibited from doing so.
The consequences are that a server wishing to halt the application must
instead of the FastCGI-specified
and suffer the consequences of not properly exiting the parse loop.