in reply to Re: thinking about mod_perl
in thread thinking about mod_perl

A technical nit, mod_perl does not use the common gateway interface.

If there is a resemblance, it is because the common gateway interface was designed based on the structure of an http request, and the commonalities between what a mod_perl job has to do and a CGI script have been intentionally exploited by the mod_perl people to make mod_perl easier to get into.

Also note that mod_perl gives access to phases of Apache's handling of an http request that PHP does not and CGI cannot. (This is both good and bad - ISPs are more inclined to give people PHP rights on servers than mod_perl because the latter is harder to restrict.)

Replies are listed 'Best First'.
Re: thinking about mod_perl
by jonadab (Parson) on Jul 22, 2003 at 17:27 UTC
    mod_perl does not use the common gateway interface

    I realise the backend is implemented differently on the server side, but the interface between the browser and the server is the same. It has to be; if it weren't, it wouldn't work without special browser support. The same is true of PHP. This is what makes the gateway interface common, is it not?

    Quidquid latine dictum sit altum viditur.
[reply]
      The browser and server talk HTTP = Hyper Text Transport Protocol. The word Gateway in CGI refers to it being a way to hook up the webserver with anything else that you want.

      In other words the CGI protocol refers only to what is happening on your server.

      PS My apologies for responding late. I am on the road and so do not have reliable net access.

[reply]

In Section Seekers of Perl Wisdom