On Mon, May 24, 2010 at 1:30 PM, Bee Jay <bee.ogra...@gmail.com> wrote: > > That's why I like the CGI gateway mechanism from ExtPascal. The CGI app > (lightweight) will run the ascociated FCGI app (the true app) if it's not yet > running. If it's already running, the CGI app acts as request proxy for the > FCGI app. As FCGI no longer got requests (went idle) for some time, it > terminates itself. So, you got CGI and FCGI advantages combined. It's also > easier during development, especially debugging. Well, for some small apps, > it might be overkill. But, for medium to large apps, with hundreds of > concurrent requests, it simply shines over plain CGI. >
"If it's already running, the CGI app acts as request proxy for the FCGI app" Would not the oposite? A FCGI lightweight app would be the proxy for some CGI apps. The FCGI stay in memory, so it is more fast for requests, while CGI app would be more specialized. Marcos Douglas _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
