What were the main disadvantages of CGI-BIN web development?

I was fortunate enough not to create cgi-bin.cgi web development. But, as a rule, those who do not seem to miss those days.

The project I recently joined with has performance issues when working with pages, which should be related to a legacy system that has a CGI-BIN-based API. This system is COGNOS 7.

The feedback I have received so far is that “COGNOS is slow”, but others have reported great success on COGNOS, I think it is more about access via CGI-BIN, rather than running COGNOS on its own .

Everything that said that are the main problems that made web development based on CGI-BIN inoperative, complicated, etc ....

+5
source share
4 answers

The main architecture problem with CGI-BIN based systems is that every HTTP request requires the server to start a new process. This affects performance in several ways:

  • It’s very expensive to start the process, like OS pages in a program, set up a process, etc.
  • Resources cannot be divided between requests, therefore, any database connections, etc. must be customized with every request.
  • User session state cannot be stored in memory, so it must be saved with every request
+4
source

CGI , CGI "" . , , ...

+1

, IMHO, , - . - HTTP HTTP-. .

0

Apache (, mod_perl), script , . , GCI, , .

0

All Articles