Nov 6, 2001, 10:16 AM Post #3 of 5 Well, there is one problem
with a CGI application. You propertly know it, but I tell it
anyway to explaiin anything below this BLOCK of text. a user
requests GET script.cgi?show=login The webserver executes the
cgi script, returns the html-page-result to the browser. The
connection is closed by the webserver. b. user fills in the
password in the recently received page, requesting POST
script.cgi action=login user=(id) password=(password) The
webserver executes the cgi script, print a html page telling
you're logged in. The connection is closed again by the
webserver., c. user enters a document, located at
script.cgi?show=topic&page=1&topic=1 The browser connects to the
webserver, the webserver executes the cgi script, returns the
html page, and the connection is closed again. That's the case
with CGI programs Do you see the (little) problem here? A HTTP
connection is created everytime you request a page. - How does
the webserver know the one connecting is still the same guy?