#23 Eliminate separate backend binary

[Sam Horrocks]

See if all of the backend functions can be moved into the CGI::SpeedyCGI
module, and then eliminate the separate speedy_backend binary and
use the normal perl binary instead.

[Nobody/Anonymous]

Logged In: NO

This is a very good idea because I will replace the
dead CgiSocket by CGI::SpeedyCGI. But the server is
running on a HP-UX node and there it is not possible
to build the backend (HP-UX is POSIX complied but
the build stops with C-Compiler errors).
A other way would be the usage of the compiler and
linker defines from Config.pm for the backend build
but the direct usage of Perl and/or XS is IMO much
better.
Silvio.Wanka@alcatel.de