webtown1.png (3102 bytes)

button_services.png (401 bytes) button_customercare.png (465 bytes) button_whatsnew.png (428 bytes) button_policies.png (341 bytes)
button_aboutus.png (378 bytes)button_contactus.png (416 bytes) button_partners.png (383 bytes) button_signup.png (338 bytes)

button2.png (368 bytes) F A Q
button2.png (368 bytes) How to FTP
button2.png (368 bytes) SSI - shtml
button2.png (368 bytes) PHP Sources
button2.png (368 bytes) CGI-BIN
button2.png (368 bytes) MySQL
button2.png (368 bytes) Apache

fp2000box.jpg (8224 bytes)


What is Common Gateway Interface?

The Common Gateway Interface (CGI) is a standard for interfacing external applications with information servers, such as HTTP or Web servers. A plain HTML document that the Web daemon retrieves is static, which means it exists in a constant state: a text file that doesn't change. A CGI program, on the other hand, is executed in real-time, so that it can output dynamic information.

For example, let's say that you wanted to "hook up" your Unix database to the World Wide Web, to allow people from all over the world to query it. Basically, you need to create a CGI program that the Web daemon will execute to transmit information to the database engine, and receive the results back again and display them to the client. This is an example of a gateway, and this is where CGI, currently version 1.1, got its origins.

The database example is a simple idea, but most of the time rather difficult to implement. There really is no limit as to what you can hook up to the Web. The only thing you need to remember is that whatever your CGI program does, it should not take too long to process. Otherwise, the user will just be staring at their browser waiting for something to happen.

Perl Main Site
Perl Scripts
PHP Scripts List
C Scripts
ASP Scripts

Copyright 1996- 2015 FiberCast Corporation
All rights reserved. Reproduction or use of any editorial or pictorial content in any manner is prohibited without express written permission of FiberCast Corporation