Women in Technology

Hear us Roar



Article:
  The PHP Scalability Myth
Subject:   CGI model vs. in-process model
Date:   2003-10-17 11:40:23
From:   anonymous2
I hate it when people talk about "CGI model vs. in-process model" or whatever. Even if your interpreter (PHP, Perl, JSP, etc) is running "in-process", you're still using CGI (assuming that the user is sending data).


CGI is not about how the web server interacts with your program - it is how the web browser sends data to the server.


If you've got something like: http://mysite.org/foo.php?key=value


You are using CGI! Sorry, just one of my pet peeves.

Main Topics Oldest First

Showing messages 1 through 3 of 3.

  • CGI model vs. in-process model
    2003-10-17 18:43:58  anonymous2 [View]

    Yes, you're right, but at this late date what are we going to call the method of web scripting where the interpreter is re-started per http request? "PRIS" (Per Request Interpreter Startup)? "Out-process" invocation? I think we're probably stuck with "cgi".
  • CGI model vs. in-process model
    2003-10-17 13:38:13  anonymous2 [View]

    CGI is all about Communicating between your Webserver and an Server-side application and how to transfer the data. See http://www.w3.org/CGI/
  • CGI model vs. in-process model
    2003-10-17 12:58:34  anonymous2 [View]

    Wrong.

    It's all about communication between the server and the program, and if you type something like:

    http://mysite.org/foo.php?key=value

    you have no idea if CGI is going on on the server. Could be the in-process model, or even something else. (Used to be, it was (almost?) always CGI).

    You need to read up.