Feature Proposal: When can one use mod_perl, fastcgi, speedycgi?

Motivation

Documentation is absent, confusing, or in some cases contradictory.

Description and Documentation

I've used TWiki for a couple years with my mod_perl2 server without problem, but have recently considered switching to fastcgi. That does not seem currently possible (partially what motivated the standalone version I gather), but it was difficult to make that determination, and I am still not 100% sure that I've got it right. Should there not be a little more explanation about TWiki's compatibility with these technologies? Or at least a sentence or two saying that in most cases they can be ignored since performance will be sufficiently fast using the standard CGI handler of Apache?

Examples

Impact

Implementation

-- Contributors: MartyBrandon - 08 Apr 2008

Discussion

I didn't understand well what is it about: to add support for other runtime technologies? Improve documentation?

Nowadays (4.2.x), TWiki supports only CGI, in the sense that official (distributed) documentation doesn't talk about other mechanisms. But CGI performance is not good in many cases, so the use of accelerators, like SpeedyCGI or ModPerl is common. TWikiStandAlone is in process of merge, so TWiki-5 will have easy support for FastCGI, ModPerl and as an HTTP Standalone server, besides plain CGI.

Each mechanism has unique features and it's up to the admin to choose the one that better fills his needs. There will be documentation about with each runtime engine.

-- GilmarSantosJr - 09 Apr 2008