I think my server is responsible for this and no addition perl modules are needed just to run fast CGI, am I right ?

No, you need a module for fast cgi same as you do for regular cgi.

Just as CGI is an interface/protocol between webservers (like apache) and programs like perl, so is FastCGI, and both protocols require both webserver and program to speak the same protocol, so that the program can speak internet (the webserver helps the program speak internet)

If you don't use a module (like a frenchtalian translator), you have to learn the protocol -- its like making your own frenchtalian speaking hammer -- just use the free one :)

In perl, CGI.pm speaks pretty good CGI, and FCGI speaks pretty good FastCGI

CGI.pm distribution even comes with CGI::Fast - CGI Interface for Fast CGI

CGI protocol is there to help programs speak internet through an intermediary known as a webserver

The best and most flexible way for perl programs to speak internet is PSGI, see PSGI::FAQ

If you use dancer or mojolicious or catalyst ... they all speak PSGI pretty well, which means they can run on mod_perl, plain old CGI, FastCGI... thats the idea behind PSGI

Dancer and CGI are just ways for computer programs to speak internet, you should learn about the internet :)

Re: How does Dancer handle forms? How do other such frameworks do it?

All the frameworks give you a request object

All the frameworks want you to give them a response object

If you're using CGI.pm and following CGI to mod_perl Porting. mod_perl Coding guidelines you're 98% modern , only 2% away from using any "modern frameworks" which have a response object

PSGI, PSGI::FAQ

If you want speed in templating, see Text::Xslate::Manual::FAQ, Xslate - Scalable template engine for Perl5